Comment #3 on issue 3322 by svenpa...@chromium.org: Segmentation fault in
GC (debug mode) with an invalid thread->context_
http://code.google.com/p/v8/issues/detail?id=3322
The garbage collector behaves like a giant verifier for the state of V8. In
your example, some object seems to have an invalid Map pointer, so you get
a crash when the GC tries to look into a Map. That is only the symptom, the
real cause is probably light years away, and usually there is a high chance
that it is in the code embedding V8, not in V8 itself: It could be
incorrect locking, overwriting of random memory, use-after-free, etc.
Use valgrind/memcheck/AddressSanitizer/ThreadSanitizer/..., use
--gc-interval=<some_relatively_small_number> to get the symptom closer to
the cause, use the debug version of v8, etc.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
