Issue 3723: CRASH @ v8::NeanderArray::length+0x4
http://code.google.com/p/chromium/issues/detail?id=3723
Comment #3 by [EMAIL PROTECTED]:
All it takes to reproduce the problem is to open a page without any
JavaScript and then
activate the debugger. Using about:blank can also be used. This is caused
by the V8 API
function v8::Debug::SetMessageHandler not ensuring that V8 is initialized.
However making v8::Debug::SetMessageHandler initialize V8 will not solve
the problem fully
as v8::Debug::SetMessageHandler is currently not called from the same
thread as JavaScript
processing for the page. The call to v8::Debug::SetMessageHandler needs to
be marshaled to
another thread as well.
This issue is not as likely to occur on [EMAIL PROTECTED], as V8 will be
initialized when loading
has finished - even for pages without JavaScript. There will still be a
race-condition
where the crash is possible.
Issue attribute updates:
Status: Started
--
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
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to chromium-bugs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
