Closed Bug 338171 Opened 18 years ago Closed 18 years ago

SeaMonkey not responding after switch from web page to desktop program and back.

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: zinnia, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.0.4) Gecko/20060510 SeaMonkey/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.0.4) Gecko/20060510 SeaMonkey/1.0.2

While on ebay clicked on my firewall traffic logs. After closing traffic logs screen, where the screen had been stayed grayed out. SeaMonkey stopped responding, even the bubbles in the icon froze. Tried clicking on my desktop, and the desktop showed but framed by SeaMonkey.Escaped by ctrl+Alt+del to close SeaMonkey.

Reproducible: Sometimes

Steps to Reproduce:
1.Open ebay page laptops>Gateway computers
2.Open personal firewall (Sygate) traffic logs
3.Close traffic logs page.(Which stays onScreen as grayed out area)
4.Click on desktop quick launch button (Desktop shows and you can even open a document but it is framed by SeaMonkey.
5.Ctrl+Alt+Delete to close SeaMonkey
Actual Results:  
SeaMonkey closed. SeaMonkey could then be reopened and would perform fine until I tried the above sequence of steps.

Expected Results:  
Sygate firewall traffic logs should have closed with the ebay open web page fully showing. SeaMonkey should have reponded.

Use modern SeaMonkey theme. I don't believe Talkback is functional yet with Win98.
Computer being used is an Athlon motherboard 1.5GHz with 512mb memory
Tried additional tests to reproduce the problem. The problem occurred only once this morning, and not once yesterday evening in 5 tries. For this reason,I suspect the event is triggered by an ad being shown occasionally on Ebay. Not sure.
Deleted Quick Time plugin as per bug forum advice. Bug problem cured.
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.