Closed
Bug 5535
Opened 26 years ago
Closed 26 years ago
[CRASH] file|open can lead to a crash
Categories
(SeaMonkey :: UI Design, defect, P1)
Tracking
(Not tracked)
M5
People
(Reporter: cmaximus, Assigned: law)
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
discovered while investigating bug 3843 ...
Seamonkey seems to often crash after opening the new window generated from selecting file|open|open.
*To Repro
It is sometimes a little tricky but basically, launch Seamonkey, select file|open and select a local html file.
Select Ok/Open as appropriate. A few times I went so far as to select file|new browser window before it crashed. I'd say it's
about 75% reproducible across the platforms if not moreso.
*Expected Result
Selecting file|open and selecting your local document should yield a new browser window with that page loaded.
*Actual Result
In most cases, after selecting the file, a new window was drawn without the chrome and apprunner crashed a couple seconds
later.
*Build info
This failure was reproduced on MacOS, RHLinux5.2, and WinNTSP4 all with the 1999042608 builds
*tidbits
The TalkBack ID for the NT crash is DZS49CED (i think, can't read my own writing) the summary reads 'file|open|crash'
The entire stdlog from the Mac crash will be included as an attachement to this bug.
Reporter | ||
Comment 1•26 years ago
|
||
I have noticed bad behavior when just opening a new browser window. I tend to
crash after opening 2 or 3 so I am not sure if it is related to the file|open
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•