Closed Bug 477374 Opened 15 years ago Closed 15 years ago

hangs with 100% CPU after alert in wizzard

Categories

(Toolkit Graveyard :: XULRunner, defect)

1.9.0 Branch
x86
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 436473

People

(Reporter: georg, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008121605

If an alerts is displayed within a wizzard it is impossible to close the alert. Instead XulRunner hangs with 100% CPU.

Reproducible: Always

Steps to Reproduce:
Reproducable with:
- Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008121605
- Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.7pre) Gecko/2009020611
Can you please give clear steps to reproduce?
Version: unspecified → 1.9.0 Branch
alert('test'); displays the alert, but it is impossible to close it. No error messages are reported to the console. It just increases CPU to 100% and never closes. Just touching the alert anywhere with the mouse is enough to increase the CPU. Probably this occurs onfocus of the alert.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Where can I fetch a XulRunner which is not a 1.9.0.x? Actual nightlies are 1.9.0.7pre. Must I build it myself fetching it from hg repository?
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.