Comment #13 on issue 15595 by christian.plesner.hansen: Crash -  
v8::internal::Invoke
http://code.google.com/p/chromium/issues/detail?id=15595

It looks like f7d6c875c48a079a above is actually a pretty rare case.  Most  
crashes in
v8::internal::Invoke seem to happen during error reporting during context  
creation
(for instance http://crash/reportdetail?reportid=528a8d8e046bd68f).  The  
errors it's
trying to report are odd -- a lot of them are RUNTIME_ASSERTs in runtime.cc  
which it
shouldn't be possible to trip, certainly not during context creation.

We can harden error reporting so we don't crash there but it's not clear  
what the
state of the vm will be afterwards.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to