Closed Bug 239025 Opened 21 years ago Closed 20 years ago

saving this url causes M17beta to crash

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: samuel, Unassigned)

References

()

Details

(Keywords: crash)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316 right-clicking and attempting to save the above-mentioned URL seems to cause mozilla to go int an infinite loop. I was able to save the file with an older version of mozilla (mozilla-1.3-0_rh8_gtk2). Reproducible: Always Steps to Reproduce: 1. go to http://www.bcgreen.com/tmp/captain-scarlet-party-beach.bmp 2. right click to 'save image' 3. run top. Actual Results: mozilla in infinite loop Expected Results: save file dialog. Note: other images I've tried worked fine.
wfm 20040328 on Win2k 20040319 on Linux.
OK: It's got something to do with my configuration using Linux 20040328, it still burps for me in my config, but if I start it with a virgin config (change $HOME, and only link over the .[xX]*, (mostly looking for .Xauthority, but too lazy to look for the name). It works just peachy. similarly if I just create a new profile. So the question, now, is whether this is worth hunting down, at all (strace, stack dump, etc.)? knowing that it's a localized problem
Keywords: crash
Samuel: Could provide TalkBack incident ID? Installer version of 1.7b contains TalkBack utility. WFM/1.7b/W2K
Severity: normal → critical
finally generated a talkback dialog (( sigabrt works... others don't seem to)). Didn't get a talkback ID: but it was submitted at about 17:48 pacific time (+= 1 minute) My clock is NTP synced Note that, in this case, I got the problem attempting to download a file from the RedVsBlue site ... (my sample link no longer seems to cause the problem (!)).
Attached file GDB tracebacks
tracebacks of sessions under GDB. Note: slightly different results under GDB If I wait 5 minutes before doing anything, mozilla will simply die and go to traceback. No rendering. No need to send SIGABRT signal. THis is clearly a different death, and due to running under GDB. Multiple sessions here. Using #comments to tell you what's going on.
Summary: saving this url causes 1.7b to crash → saving this url causes M17beta to crash
Do you still crash using Mozilla 1.7rc2 ? If so, please post Talkback Incident ID for this crash by running "mozilla/components/talkback/talkback"
Samuel: Could you reproduce crash with Mozilla 1.7 final? Could you provide TalkBack incident ID of such crash?
Can't do much without a Talkback ID...so can't say if this is a topcrasher, but adding topcrash- to get this on my radar. If anyone else is able to reproduce this crash, please provide a Talkback ID. Thanks! If we don't hear from anyone, might be worth marking this WFM.
Product: Browser → Seamonkey
WFM, please reopen if you see this with a recent nightly or can come up with a reproducible testcase.
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.

Attachment

General

Creator:
Created:
Updated:
Size: