Closed Bug 230764 Opened 22 years ago Closed 19 years ago

go to weather.com, get flash ad ( without flash plugin ), see mozilla die

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: dantealiegri, Assigned: blizzard)

References

()

Details

(Keywords: crash, Whiteboard: dupeme? possible dupe of 169322)

Attachments

(2 files)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031225 Firebird/0.7 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040110 Flash is killing mozilla, it is when a page first loads, I'm not sure if it is when going somewhere after being at a place with flash, or going into a place with flash. Reproducible: Always Steps to Reproduce: 1.goto weather.com without flash plugin installed. 2.reload a few times. 3.see mozilla die. Actual Results: mozilla crashes. Expected Results: mozilla not dead, with a page blissfuly absent of flash. May be limited to linux gtk2 ( optimized? ) builds. haven't tested.
Attached file Backtrace of crash
Keywords: crash
No, I do not crash with a gtk1 build. I had be using my own build, but I also nabbed a gtk2 FB build when getting the gtk1 tar, and that crashes as well, so it is not my build options.
Yuck. Could be flash, could be us. Hard to say.
Blocks: gtk2
> Flash is killing mozilla, > 1.goto weather.com without flash plugin installed. to be perfectly clear... you don't have the flash plugin installed. When you visit weather.com, you get the plugin puzzle piece instead of a flash animation, right?
Correct. I load weather.com. I get the "Plugin not installed Press OK to get it". I press either one, weather.com loads with the puzzle piece. I was flourishing a bit by saying "Flash is killing mozilla" .. what I should have said was "the use of flash in webpages seems to be killing mozilla".
on a hunch, I downgraded gtk/glib/pango to 2.2, and the crash no longer happens.
worksforme with linux turnk CVS with gtk2/xft can you build with symbols and grab a stack trace?
> on a hunch, I downgraded gtk/glib/pango to 2.2, and the crash no longer happens. what had you been using before? 2.4?
well, there is no gtk 2.4 yet -- I was using 2.3, if that is what you meant.
The problem here is that the logic of when to call XSync() in gtk2xtbin.c is not correct, so changes in exact sequences of operation or timing with GTK+-2.3 cause it to crash. XSync should be called: - When a resource has been created in GTK+, and the code needs to make sure that it exists on the server before making an Xt call on a different display (call XSync on the GTK+ display by calling gdk_flush()) - When a resource has been created in Xt, and the code needs to make sure that it exists on the server before making a GDK call on a different display (call XSync on the Xt display) - Before removing an error trap when X calls have been made that are not round trip. (I don't believe the code actually needs error traps when the first two rules are followed, however.)
Status: UNCONFIRMED → NEW
Ever confirmed: true
This may be a dupe of bug 169322
Whiteboard: dupeme? possible dupe of 169322
Drew: Are you still seeing this? (WFM with gtk 2.10)
No, I haven't been able to recreate this since mid-2005.
No longer reproduceable. Please comment or reopen if this problem returns. -> INVALID
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: