Closed Bug 774680 Opened 12 years ago Closed 11 years ago

Intermittent test_websocket.html | application timed out after 330 seconds with no output ("ASSERTION: nsScriptSecurityManager not thread-safe: '_mOwningThread.GetThread() == PR_GetCurrentThread()', file nsScriptSecurityManager.cpp, line 449")

Categories

(Core :: Networking: WebSockets, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: emorley, Unassigned)

References

Details

(Keywords: assertion, intermittent-failure)

Rev3 WINNT 5.1 services-central debug test mochitests-1/5 on 2012-07-15 20:34:20 PDT for push c2760174d698

slave: talos-r3-xp-075

https://tbpl.mozilla.org/php/getParsedLog.php?id=13563392&tree=Services-Central

{
42502 INFO TEST-PASS | /tests/content/base/test/test_websocket.html | shouldn't connect yet in test-2!
42503 INFO TEST-PASS | /tests/content/base/test/test_websocket.html | the ws connection in test 18 shouldn't be closed cleanly
nsStringStats
 => mAllocCount:         681004
 => mReallocCount:        61527
 => mFreeCount:          621856  --  LEAKED 59148 !!!
 => mShareCount:        1129566
 => mAdoptCount:          75756
 => mAdoptFreeCount:      75753  --  LEAKED 3 !!!
###!!! ASSERTION: nsScriptSecurityManager not thread-safe: '_mOwningThread.GetThread() == PR_GetCurrentThread()', file e:/builds/moz2_slave/srv-cen-w32-dbg/build/caps/src/nsScriptSecurityManager.cpp, line 449
TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | application timed out after 330 seconds with no output
args: ['C:\\talos-slave\\test\\build\\bin\\screenshot.exe', 'c:\\docume~1\\cltbld\\locals~1\\temp\\mozilla-test-fail_nl5h4g']
SCREENSHOT: <snip>

command timed out: 1200 seconds without output, attempting to kill
SIGKILL failed to kill process
using fake rc=-1
program finished with exit code -1
}

(See also bug 766915)
Blocks: 774711
Whiteboard: [orange]
(OrangeWFM bugs not touched for 2 months)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.