https://tbpl.mozilla.org/php/getParsedLog.php?id=10188239&tree=Fx-Team Rev3 Fedora 12x64 fx-team pgo test mochitest-other on 2012-03-19 13:12:22 PDT for push 90d3b1fb284d TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/toolkit/components/aboutmemory/tests/test_memoryReporters.xul | Exited with code 1 during test run INFO | automation.py | Application ran for: 0:01:55.389786 INFO | automation.py | Reading PID log: /tmp/tmpzgNwE8pidlog ==> process 2229 launched child process 2262 ==> process 2229 launched child process 2271 ==> process 2229 launched child process 2279 ==> process 2229 launched child process 2281 ==> process 2229 launched child process 2283 INFO | automation.py | Checking for orphan process with PID: 2262 INFO | automation.py | Checking for orphan process with PID: 2271 INFO | automation.py | Checking for orphan process with PID: 2279 INFO | automation.py | Checking for orphan process with PID: 2281 INFO | automation.py | Checking for orphan process with PID: 2283 Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-linux64-pgo/1332183603/firefox-14.0a1.en-US.linux-x86_64.crashreporter-symbols.zip PROCESS-CRASH | chrome://mochitests/content/chrome/toolkit/components/aboutmemory/tests/test_memoryReporters.xul | application crashed (minidump found) Crash dump filename: /tmp/tmpIwyC_p/minidumps/3c99980a-ba74-7d24-4a1e436e-04c8eeae.dmp Operating system: Linux 0.0.0 Linux 2.6.31.5-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64 CPU: amd64 family 6 model 23 stepping 10 2 CPUs Crash reason: SIGSEGV Crash address: 0x10 Thread 0 (crashed) 0 libpthread-2.11.so + 0x8db0 rbx = 0x00000000 r12 = 0xff893660 r13 = 0xff89360f r14 = 0x6b7dd010 r15 = 0xff893660 rip = 0xd3608db0 rsp = 0xff893598 rbp = 0x00000001 Found by: given as instruction pointer in context 1 libnspr4.so!PR_Lock [ptsynch.c:90d3b1fb284d : 206 + 0x4] rip = 0x97de70a9 rsp = 0xff8935a0 Found by: stack scanning 2 libxul.so!mozilla::dom::workers::WorkerPrivate::BlockAndCollectRuntimeStats [Mutex.h : 106 + 0x8] rbx = 0x6b7dd000 rip = 0x9517223a rsp = 0xff8935b0 Found by: call frame info 3 libxul.so!WorkerMemoryReporter::GetExplicitNonHeap [WorkerPrivate.cpp:90d3b1fb284d : 223 + 0xe] rbx = 0x6562c440 r12 = 0x06a9d000 r13 = 0xff893680 r14 = 0x96626290 r15 = 0xff893660 rip = 0x95172349 rsp = 0xff893600 rbp = 0x00000000 Found by: call frame info 4 libxul.so!nsMemoryReporterManager::GetExplicit [nsMemoryReporterManager.cpp:90d3b1fb284d : 805 + 0x9] rbx = 0xff893a50 r12 = 0x06a9d000 r13 = 0xff893680 r14 = 0x96626290 r15 = 0xff893660 rip = 0x9574a682 rsp = 0xff893620 rbp = 0x00000000 Found by: call frame info 5 libxul.so!NS_InvokeByIndex_P [xptcinvoke_x86_64_unix.cpp : 195 + 0xb] rbx = 0xff893a50 r12 = 0x00000000 r13 = 0x00000002 r14 = 0x95d45bf4 r15 = 0x96933cb8 rip = 0x9574c57a rsp = 0xff893740 rbp = 0xff893820 Found by: call frame info

So, as you can see up above, this apparently got fixed on the trunk at the end of March, but then became permaorange on Linux64 on Aurora with https://hg.mozilla.org/releases/mozilla-aurora/rev/8d0f70b87fba (which seems like an unlikely thing to break this in such an unlikely way). We really should do something about that permaorange other than just keep starring it, and because it takes down the whole suite, not having mochitest-chrome on 13, for another 12 weeks.

This issue seems to be perma-orange on aurora Linux 64-bit PGO builds.

s/aurora/beta/, only 12 more weeks of permaorange!

Not to worry, those aren't it spreading to 14, just the last two from 13 on Aurora.

This is perma-orange on beta 13 since uplift yesterday. (5 out of 5 runs failed so far.)

(In reply to Matt Brubeck (:mbrubeck) from comment #53) > This is perma-orange on beta 13 since uplift yesterday. (5 out of 5 runs > failed so far.) Filed bug 749010.

I'm hitting this permanently with debug try builds for bug 754671: https://tbpl.mozilla.org/?tree=Try&rev=a366582689c4 The patch introduces a ChromeWorker for async file IO. Does this maybe help to hunt it down?

The crashes I see are only in debug builds (which is confirmed by the fix). This bug seems about PGO builds, only.

Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of: {random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open} There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.