ASSERTION: Potential deadlock | timeout in js1_5/Array/regress-94257.js

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
13 years ago
6 years ago

People

(Reporter: bc, Unassigned)

Tracking

({regression})

1.8 Branch
x86
Linux
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
In 20060415 debug browser 1.8.0 and 1.8 builds I showed timeouts in js1_5/Array/regress-94257.js. I could not reproduce any hangs, but did see 

ASSERTION: Potential deadlock between Monitor@... and Lock@... in xpcom/threads/nsAutoLock.cpp line 302.

This timeout behavior on these tests in new since at least 2006-04-10.
Bob, this is not a JS engine bug.  That assertion may or may not be related to the hang, but if the hang is a deadlock, then it likely is.

Can you get stacks from all the threads, using gdb or VS.NET or whatever's going, once the process is hung?  Also, get into the debugger with XPCOM_DEBUG_BREAK=trap set in the environment, continue past whatever bogus assertions you have to, and when the test hits the Potential deadlock, find me on IRC.  It should be easy to track down the offending code.

Bouncing to XPCOM for now, but this will probably end up elsewhere.

/be
Component: JavaScript Engine → XPCOM

Comment 2

13 years ago
-> default owner
Assignee: general → nobody
QA Contact: general → xpcom

Comment 3

13 years ago
What are the steps to run this test to reproduce this bug?
(Reporter)

Comment 4

13 years ago
Forgot to mention, debug builds only.

To run the test standalone in the browser:
<http://test.bclary.com/tests/mozilla.org/js/js-test-driver-standards.html?test=js1_5/Array/regress-94257.js;language=language;javascript>

To reproduce the environment used in the automated test, install Spider <http://bclary.com/projects/spider/spider/spider.xpi>

Then launch Spider as a XUL apps with chrome url <chrome://spider/content/spider.xul?url%3Dhttp%253A%252F%252Ftest.bclary.com%252Ftests%252Fmozilla.org%252Fjs%252Fjs-test-driver-standards.html%253Ftest%253Djs1_5%252FArray%252Fregress-94257.js%253Blanguage%253Dlanguage%253Bjavascript%26depth%3D0%26timeout%3D120%26waittime%3D0%26hooksignal%3Don%26autostart%3Don%26autoquit%3Don%26javascripterrors%3Don%26javascriptwarnings%3Don%26csserrors%3Don%26scripturl%3Dhttp%3A%2F%2Ftest.bclary.com%2Ftests%2Fmozilla.org%2Fjs%2Fuserhookeach-js.js>

e.g. ./firefox -chrome chrome://blah.

The app should load and run the test and quit when finished.

(Reporter)

Comment 5

13 years ago
this is 1.8.0 and 1.8 only. 
Version: Trunk → 1.8 Branch

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.