Closed Bug 330888 Opened 20 years ago Closed 18 years ago

Crash following form submission

Categories

(SeaMonkey :: General, defect)

1.8 Branch
x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: dave127001, Unassigned)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0 Clicking the "details" tab (a JavaScript-driven form) from PubMed (<http://www.ncbi.nlm.nih.gov/entrez/query.fcgi>) often triggers a crash. Reproducible: Sometimes Steps to Reproduce: 1. Visit http://www.ncbi.nlm.nih.gov/entrez/query.fcgi 2. Submit query (optional). 3. Click the "details" tab. Actual Results: Crash. Windows reports "pipboot.dll" as the faulting component in the crash report (xxxx_appcompat.txt). I'm not sure what the variable is that only causes it to crash sometimes. It is worth mentioning that I have "security.warn_submit_insecure" set to true (which is the default setting, but I suspect it is frequently disabled by most/many users).
It further appears that this behavior is only observed when more than one tab is open.
Do you crash with a clean profile? Can you try a trunk build: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ and send in a talkback report if that crashes?
Keywords: crash
Version: unspecified → 1.8 Branch
(In reply to comment #2) > Do you crash with a clean profile? Yes (just tested). I left all of the settings at their defaults, and with https://buzilla.mozilla.org in one browser tab, opened a new tab with the URL in the bug report. Clicking the "details" form button caused a crash on the first attempt. That was using the same Seamonkey release as originally reported (1.0). > Can you try a trunk build: > http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ > and send in a talkback report if that crashes? > I have not had an opportunity to try that yet.
The problem is still present with Seamonkey 1.01. I do not want to download and test a nightly build unless others are unable to reproduce the bug.
1.1.9 doesn't crash. Could you please see if you still experience this issue with a newer release of SeaMonkey? Feel free to reopen if you do. http://www.seamonkey-project.org/releases/
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.