Closed Bug 63230 Opened 24 years ago Closed 24 years ago

crash on exit

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: akkzilla, Assigned: asa)

Details

(Keywords: crash)

For several weeks, sweetlou linux trunk builds have crashed on exit for me, every time (run mozilla, immediately quit, boom). Happens with every build I've downloaded in the last three weeks. I don't have a stack trace (optimized builds) and these builds no longer include fullcircle, so all I know is the message printed out: u/akkana/nstrunk1218/run-mozilla.sh: line 29: 21265 Segmentation fault $prog ${1+"$@"} No core file is left in the directory where mozilla lives. My own debug builds don't crash on exit, just the sweetlou optimized builds (I download the net installer, and install as myself to a subdir of my home directory with custom so that I can turn off the en-de language pack, but leave the rest of the defaults checked).
Keyword crash.
Keywords: crash
Many crash-on-exit bugs the past days. Dup of 62931?
I don't think so, because I can close browser windows without crashing as long as they're not the last window open (i.e. as long as the app doesn't need to exit). But the two bugs might be related.
I've just built an optimised build from the tip and mine crashes on closing all sorts of windows. I have once been able to load the brower (blank page), close and segfault, other times it's not reproducable. I also crashed while closing the Prefs window once. Debian Unstable, gcc 2.95.3.
more like bug 62643?
Akkana, still seeing this? If you get the stub installer build and do a full or custom install it should have a working talkback component. For what it's worth I'm not seeing it with 2001022308 mozilla linux installer builds.
I'm no longer seeing this in release builds.
Marking WORKSFORME as per Asa's and Akkana's comments.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.