Closed
Bug 194856
Opened 22 years ago
Closed 22 years ago
Crashes repeatedly when opening specified URL
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: swatts, Assigned: asa)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.2.1) Gecko/20021130
As of today (2003-03-25), opening the URL causes Moz to crash with the following
Windoz dialog:
Windows - Application Error
The instruction at 0x77f83a65 referenced memory at 0x39393939. The memory could
not be "written".
Other pages seem ok (so far), and I have visited that page with the Mozilla from
the same machine in the past, so something has changed there to cause Moz to dump.
Reproducible: Always
Steps to Reproduce:
1. Enter URL: http://sourceforge.net/projects/cygnome in address field
2. Press enter
3.
Actual Results:
Mozilla dumps.
The Windows Application Error dialog appears most of the time, but not always.
The referenced memory address appears the same each time, I dont know if the
instruction address is constant though.
Expected Results:
Display the page.
Mozilla has displayed this page correctly in the past, and so suspect a recent
change there, which may not persist?
Reporter | ||
Comment 1•22 years ago
|
||
OK, after reporting the bug, I can now view the page without problem.... grrr..
Comment 2•22 years ago
|
||
WFM - 1 day old CVS based trunk build - WinXP-Sp1.
Reporter : try with a younger release, like 1.3b.
WFM, day old CVS, linux.
Reporter: WHen crashes occur, the best you can do is to allow Talkback to submit
crash data, then include the talkback ID in the bug-report.
That way it's easyer to determine what this might be a duplicate of.
Since you too say it works now, however - resolving as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•