557634 - Crash when Firebug open and Flash requests the same FLV twice

Status: RESOLVED DUPLICATE of bug 546851

(Firefox :: General, defect)

Description

[Rob]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

Loading a Flash widget that requests two identical FLVs and stops the load (this is to get the first frame for a thumbnail) will crash Firefox when Firebug is open 100% of the time. When Firebug is not open I think it still may crash but very seldom and maybe unrelated.

Reproducible: Always

Steps to Reproduce:
To reproduce it under Firefox 3.6.3 do the following:
1. Create a new profile
2. Install the latest version of Firebug
3. Enable the network panel
4. Delete the cache via "Tools"->"Clear Recent History..." to be sure nothing is in there, but DON'T DISABLE THE CACHE!
5. Load the page http://seed.sproutbuilder.com/cQBH98B8KxbujU-k and open Firebug
while the page is loading
Actual Results:  
Firefox crashes

Expected Results:  
Firefox does NOT crash and both videos play fine.

I tested this with the four combinations of FF 3.6.3/3.7a4pre and Firebug 1.5.3/1.6X.0a8 under Windows 7. I could reproduce this with both versions of Firebug under FF 3.6.3, but not under 3.7a4pre. So this is obviously fixed by the Mozilla guys in the new version of Firefox. Is there a chance we can get this out in a 3.6.x release?

You can't reproduce this when the cache is disabled or the page is reloaded via Ctrl+F5. Just when the cache is enabled but empty when loading the page it crashes. And also just when Firebug is enabled (doesn't matter which tab is selected at that time). When it's suspended, everything is fine. Hope I could help with this information.

Comment 1

[Matthias Versen [:Matti]]

Do you have a crash ID :
https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report

Comment 2

[zug_treno]

Duplicate of Core bug 546851 -> Core bug 540566?