342278 - crash on flight search form on Swiss.com

Status: VERIFIED DUPLICATE of bug 210931

(Firefox :: General, defect)

Description

[Mikhail Ramendik]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.2 (like Gecko) (Debian)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060406 Firefox/1.5.0.4 (Debian-1.5.dfsg+1.5.0.4-0bpo1)

When one enters flight data (from/to airport, date) on the swiss.com main page and ties to search for flights, Firefox crashes.

Reproducible: Always

Steps to Reproduce:
1. Enter http://www.swiss.com
2. On the front page, fill some airtport names into the From and To fields
3. Click on "Search flights"

Actual Results:  
Firefox crashed

Expected Results:  
Search page from Swiss.com should be loaded

Happens both with 1.0.x from Debian sarge and 1.5.x from Debian sarge backports

Comment 1

[Patrick]

wfm
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060620 Minefield/3.0a1

Do you have a stack for the crash?

Comment 2

[Mikhail Ramendik]

Could you tell me how to get the stack? I could not identify the binary to run in gdb; /usr/bin/firefox is a complicated script and gdb won't run it.

Comment 3

[Philip Withnall (unavailable)]

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9a1) Gecko/20060620 Minefield/3.0a1 - Build ID: 0000000000
WFM.

You've got two alternatives: you could try to reproduce it with an official Mozilla build of Firefox, and if you can, send a Talkback report, and post the Talkback ID here. (http://kb.mozillazine.org/Talkback)

Or, you could continue with Debian's build, and get a stack trace using gdb by attaching it to a currently running Firefox process.

Comment 4

[Mikhail Ramendik]

For some reason firefox hangs as soon as I attach gdb to its process.

Where can I find a document on installing and running a talkback-enabled build without disrupting an existing system?

Comment 5

[Mikhail Ramendik]

But now I have seen it crash while in started a terminal window, and here's what it says.

The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 62905 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Comment 6

[Mikhail Ramendik]

A guru has helped me get attaching gdb to work, but the proigram just exits. I tried setting a breakpoint on gdk_x_error but the function is not defined. Apart from rebuilding the entire gtk stack with symbols (not a very promising thing regarding the stability of my sarge system...), is there anything I can do to get a backtrace?

Alternatively, perhaps someone with a more debug-friendly setup could reproduce the issue?

Comment 7

[timeless]

no thanks. first:

./firefox -g

should get you a happy debugger (if it doesn't, ./run-mozilla.sh -g ./firefox-bin should.)

you should read http://www.mozilla.org/unix/debugging-faq.html

if you're going to file bugs against mozilla, then we expect you to build your own builds --enable-debug --disable-strip and not use Debian builds, see http://www.mozilla.org/bugs/
(you're generally welcome to file bugs using mozilla.org builds, which are of course the builds with talkback, although as it happens for the error here does not trigger talkback as it's gdk killing us instead of us crashing. (If you want to use a vendor's build, then you're expected to complain to your vendor when it crashes.)

the instructions to build mozilla really aren't that bad. especially on Unix. note that they don't involve installing mozilla into your system directories, doing such is just some insanity of distro vendors.

you're also expected to read and follow directions from error messages, especially ones that say things like "To debug your program, run it with the --sync command line option to change this behavior."

that said, the badalloc you see should be a duplicate of a bug we have in our system with a fairly large patch, so once you've reproduced the badalloc, you should visit bug 210931 and see about testing the patch there, hopefully someday it might be committed.

Comment 8

[Stephanie Daugherty [:sdaugherty]]

wfm, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
wfm,  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/2006112704 Minefield/3.0a1
although, from the notes it looks like this bug's platform specific.

Previous comment by timeless says to dupe against 210931, could someone please do so?

Comment 9

[Carsten Book [:Tomcat]]

No Response from Reporter for over 3 Months.

Resolving this as Dupe of 210931, because of comment #7 and status Whiteboard

*** This bug has been marked as a duplicate of 210931 ***