Bug 54034
| Summary: | ScriptExecutionContext shutdown is a bit of a mess | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jeremy Orlow <jorlow> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | abarth, ap, cmarcelo, dgrogan, eric, fishd, gregsimon, jorlow |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Jeremy Orlow
Message ports are closed in "stopActiveDOMObjects". The function should probably be renamed or split in two.
The blob stuff is shut down in ~ScriptExecutionContext, but the object is ref counted, so when this happens is not deterministic. It should probably be done with the message ports are closed, but...
void FrameLoader::frameDetached() does |m_frame->document()->stopActiveDOMObjects();| and then |detachFromParent();| which fires the unload handlers. So, in theory, new active dom objects or message ports could be created there, right?
Perhaps there are other problems as well? I'm not an expert on this stuff, but I'm happy to take a crack at cleaning it up.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |