171445 - Inconsistent crash on form submission in embedding context when compiled with gcc 3+

Status: RESOLVED WORKSFORME

(Core Graveyard :: Embedding: GTK Widget, defect)

Description

[Philip Langdale]

This one has been floating around for a while now, but hasn't recieved serious
attention until the big push to use gcc 3.2.

On an inconsistent basis, in gtk embedded mozilla, there will be a crash in
|EmbedProgress:RequestToURIString| when it attempts to |GetURI| from the channel.

This has been observed a lot in galeon. see: 

http://bugzilla.gnome.org/show_bug.cgi?id=67691

And I have successfully reproduced it in TestGtkEmbed.

The given url is a simple form submission. Choose a radio item and submit.
Repeat until crash. There's no consistent pattern, indicating evil memory leak
type behaviour behind the scenes.

This is critical for embedded mozilla, and would be a blocker if it affected all
compilers.

Comment 1

[Yanko Kaneti]

*** Bug 117416 has been marked as a duplicate of this bug. ***

Comment 2

[Tommi Komulainen]

FYI,

I've been using gcc-3.2 built galeon2 for quite a long time and not once
has galeon crashed on me.  I tried the linked URL but got bored because
galeon just wouldn't crash. :)

I'm building mozilla with -O2 -march=i686 -mcpu=i686 -fomit-frame-pointer
-maccumulate-outgoing-args, and galeon otherwise with the same flags except 
without the -fomit-frame-pointer.

HTH.

Comment 3

[Joshua Ginsberg]

I'd love to vote for this bug, but Galeon2 (1.3.0, gcc 3.2) crashes when I try
to vote, Galeon crashes. Consistently. I've tried it four times.

*sigh* This is a pretty big pain in my ass.

-jag

Comment 4

[Tavis Ormandy]

WFM after upgrading, so it Appears to be fixed in Mozilla 1.2, Galeon 1.2.7. Woohoo!

$ gcc --version
gcc (GCC) 3.2.1
<...>
$ /lib/libc.so.6 
GNU C Library stable release version 2.3.1, by Roland McGrath et al.
<...>
$ mozilla --version
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021126, build 2002112613
$ galeon --version
Gnome galeon 1.2.7

Comment 5

[Philip Langdale]

Seems to be fixed. Not getting reports with new configurations and certainly
can't repro. As we never established the cause of the problem and how it was
fixed, I'm makring WORKSFORME