Updates:
Status: Available
Owner: ---
Cc: s...@chromium.org
Comment #6 on issue 6418 by cr...@chromium.org: Chrome: Crash Report -
Stack Signature: -487E8E
http://code.google.com/p/chromium/issues/detail?id=6418
I've looked at this more, but I'm going to unassign it-- I don't have more
time to spend on it this week and
can't find a way to reproduce it.
My current hypothesis is either that something has overwritten the process_
member of the RenderViewHost
or that the RenderViewHost itself has been deleted and the memory has been
reallocated to something else.
The fact that 0x20 is on the stack could be because process_ is null and
the accessor function (or the call to
Init()) is inlined.
I'm not aware of a way for a RenderViewHost to be created with a null
process, since it looks like
SiteInstance::GetProcess prevents that.
Since we don't know how to reproduce this, is there a check or guard we can
add to provide more information
in future stack traces of this crash?
Sorry I can't look more for now.
--
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
-~----------~----~----~----~------~----~------~--~---
