Issue 2855: safe browsing/malware detected crash
http://code.google.com/p/chromium/issues/detail?id=2855

Comment #10 by [EMAIL PROTECTED]:
Here is what is happening. Selecting the text described in the initial  
report is
actually irrelevant.

1. The first navigation happens, a pending entry is created for the URL  
that requires
the interstitial. The interstitial is displayed while the entry is pending.

2. When the user navigates back (they can use the back button or press the  
get me out
of here button) the browser process will tell the renderer to cancel the  
load for the
initial page.

3. The user then navigates to the same URL again with another interstitial.  
A new
pending entry is created and the interstitial is displayed.

4. The first load's "error" message is now received, which was originally  
sent by the
renderer in step 2. It could be delayed for a number of reasons in IPC or  
on the I/O
thread of the browser.

5. RenderViewHost::OnMsgDidFailProvisionalLoadWithError calls  
WebContents::DidFailProvisionalLoadWithError which sees that there is  
indeed a
pending entry and the URLs match. It calls  
NavigationController::DiscardPendingEntry.

6. Deleting the pending entry triggers tab contents collection while the  
second
interstitial is displayed and the load is still pending. This eventually  
causes a
crash.

There are two issues: (1) we shouldn't crash when we receive random  
messages from the
renderer at random times, and (2) we should be able to tell that the error  
message
was actually from the first load and not the second.



-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to