[Webkit-unassigned] [Bug 80165] [Qt][WK2] Crash in Frame.cpp when loading index.hu

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=80165





--- Comment #8 from Zalan Bujtas <zbujtas at gmail.com>  2012-03-05 08:05:25 PST ---
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > > (In reply to comment #4)
> > > > so how did we end up with suspended frames while loading? Is it normal to see suspendActiveDOMObjectsAndAnimations() calls at this phase of constructing a page?
> > > 
> > > No, but if the page is loading continuously via xmlhttprequest, then it is inevitable we will end up with a suspended frame during a pan while a xmlhttprequest is running.
> > 
> > I can repro crash without any page interaction (panning, zooming) by just simply loading the page.
> 
> I meant the second assertion we are seeing after guarding m_doc is triggered by page interaction.
> 
> You are right though, the first one crash is actually a bit odd. It is a unset document call so probably during a redirection or reload of something in the page, but there still shouldn't be any calls suspending active-dom-objects before the users starts interacting with the page. 
> 
> It could be that flickable is interpreting some reported state-changes from the WebProcess as a user-input and starts animating them.

Yea, could very well be. Before the if (document()) check is added (which seems to be checked everywhere in setDocument, so having null m_doc looks like a valid state), we should see why the suspend is triggered in this case. Having DOM objects suspended while loading (and resumed at some point) could potentially make complete load time longer. (so i guess in that sense, it's good that we've got this crash, otherwise it would have gone unnoticed)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.