Closed Bug 482420 Opened 15 years ago Closed 3 years ago

tsspider fails with "browser frozen" on windows

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: sicking, Unassigned)

Details

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1236656400.1236668687.31791.gz


Doesn't look like any checkins in the range are to blame since I don't think they touch any code that runs during the tsspider tests. Here is the checkin range just in case:

http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=522eb5aff398&tochange=ba3ad61aa365


Relevant part of the log:

NOISE: Cycle 5: loaded http://localhost/page_load_test/sunspider/bitops-bitwise-and.html (next: http://localhost/page_load_test/sunspider/bitops-nsieve-bits.html)
NOISE: Cycle 5: loaded http://localhost/page_load_test/sunspider/bitops-nsieve-bits.html (next: http://localhost/page_load_test/sunspider/controlflow-recursive.html)
NOISE: Cycle 5: loaded http://localhost/page_load_test/sunspider/controlflow-recursive.html (next: http://localhost/page_load_test/sunspider/crypto-aes.html)
NOISE: Cycle 5: loaded http://localhost/page_load_test/sunspider/crypto-aes.html (next: http://localhost/page_load_test/sunspider/crypto-md5.html)
Failed tsspider: 
		Stopped Tue, 10 Mar 2009 00:03:53
FAIL: Busted: tsspider
FAIL: browser frozen
program finished with exit code 0
TinderboxPrint:id:20090309204000

TinderboxPrint:<a href = "http://hg.mozilla.org/mozilla-central/rev/ba3ad61aa365">rev:ba3ad61aa365</a>

TinderboxPrint:FAIL: Busted: tsspider

TinderboxPrint:FAIL: browser frozen
OS: Mac OS X → All
Hardware: x86 → All
Summary: tsspider fails with "browser frozen" → tsspider fails with "browser frozen" on windows
Was this a one time event or is this reoccurring? Was this on the tinderbox or offline?
There was a merge from Tracemonkey earlier in the day, it's possible we picked up something that caused an intermittent hang in Sunspider.
haven't seen this on tm
Assignee: general → nobody

Old bug, no longer valid.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.