Closed
Bug 196883
Opened 21 years ago
Closed 20 years ago
Mozilla crashes when I try to fill in information on FAFSA's web site.
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jon, Unassigned)
References
()
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030305 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030305 At https://fafsa.ed.gov/FOTWWebApp/AppStatServlet, fill in a sample social security number. Upon entering a digit, mozilla crashes. Reproducible: Always Steps to Reproduce: 1. Go to https://fafsa.ed.gov/FOTWWebApp/AppStatServlet 2. Fill in a sample social security number 3. Mozilla crashes Actual Results: Mozilla crashes Expected Results: Mozilla does not crash Running Mozilla 20030305 on Debian Unstable. Tested on Mozilla 1.2.1 on Windows 2000 but it doesn't crash there.
|
||
Comment 1•21 years ago
|
||
Works for me, build ID 20030310 on solaris 8/sparc using gtk2. No crash while typing into the form.
|
||
Comment 3•21 years ago
|
||
are you using a .mozilla.org build? please provide a talkback ID
Keywords: crash
I am using mozilla-browser-snapshot version 0.0.20030305.09.trunk-1 in Debian Unstable; I originally discovered the bug in Galeon, but verified that the bug still occurs when running mozilla. I don't think I have talkback installed... ?
|
|
||
Comment 5•21 years ago
|
||
builds from Debian won't have. please grab a stacktrace from gdb (assuming Debian didn't strip all the symbols) or try a build from .mozilla.org: http://download.mozilla.org/pub/mozilla/nightly/ ==> form controls
Assignee: saari → form
Component: Event Handling → Layout: Form Controls
I believe Debian strips the symbols: jon@host:~$ gdb mozilla-snapshot GNU gdb 5.3-debian Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"..."/usr/bin/mozilla-snapshot": not in executable format: File format not recognized (gdb) run Starting program: No executable file specified. Use the "file" or "exec-file" command. I tried the 2003031205 build from mozilla.org and it did not experience the crash, so guess it's been fixed since 20030305 (the date of my Debian build). I'll come back if the next Debian update still crashes.
|
|
||
Comment 7•21 years ago
|
||
"mozilla-snapshot" is probably a script. You would need to start Mozilla normally, attach gdb to Mozilla, and then make it crash.
Ah. So that's why it didn't work. I tried attaching gdb to the running process, but mozilla would not redraw the screen when gdb was attached to it. I instead followed the directions at http://www.mozilla.org/unix/debugging-faq.html, but the Debian snapshot was compiled without debugging symbols. Here's what I got: GNU gdb 5.3-debian Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...(no debugging symbols found)... (gdb) run Starting program: /usr/lib/mozilla-snapshot/mozilla-bin (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 1683)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... An error occurred reading the startup configuration file. Please contact your administrator. line 7: SyntaxError: syntax error. pref("font.FreeType2.enable", ); (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 32769 (LWP 1685)] [New Thread 16386 (LWP 1686)] [New Thread 32771 (LWP 1687)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 49156 (LWP 1688)] (no debugging symbols found)...[New Thread 65541 (LWP 1689)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 81926 (LWP 1690)] [New Thread 98311 (LWP 1691)] [New Thread 114696 (LWP 1692)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 131081 (LWP 1693)] [New Thread 147466 (LWP 1694)] [New Thread 163851 (LWP 1695)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 180236 (LWP 1696)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 196621 (LWP 1698)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 1683)] 0x40b3dd44 in NSGetModule () from /usr/lib/mozilla-snapshot/components/libgklayout.so
|
||
Comment 9•20 years ago
|
||
(In reply to comment #6) > I tried the 2003031205 build from mozilla.org and it did not experience the > crash, so guess it's been fixed since 20030305 (the date of my Debian build). > I'll come back if the next Debian update still crashes. > Shouldn't this bug be resolved INVALID or WORKSFORME? First because it was filed against a Debian build and again because an official Mozilla.org build doesn't have it? And (now that I tested it myself) for a third reason, I was unable to produce this crash with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040411
|
|
||
Comment 10•20 years ago
|
||
I'm going to mark this WFM. I didn't realize the dates all said 2003 not 2004... Reporter, if you can still see this bug with a recent nightly from mozilla.org, then feel free to reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•