Closed Bug 962859 Opened 11 years ago Closed 11 years ago

Intermittent ABORT: CRT ERROR HEAP CORRUPTION DETECTED | TEST-UNEXPECTED-FAIL | /tests/dom/indexedDB/test/test_webapp_clearBrowserData_inproc_inproc.html | application terminated with exit code 2147483651

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
28 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
firefox29 --- affected

People

(Reporter: mbrubeck, Unassigned)

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=33419227&tree=Mozilla-Aurora Windows XP 32-bit mozilla-aurora debug test mochitest-3 on 2014-01-22 14:28:51 PST for push 1a55393434e0 slave: t-xp32-ix-043 14:42:15 INFO - 23539 INFO TEST-START | /tests/dom/indexedDB/test/test_webapp_clearBrowserData_inproc_inproc.html 14:42:15 INFO - --DOCSHELL 0EE3AD00 == 12 [pid = 1952] [id = 39] 14:42:15 INFO - --DOCSHELL 0F170028 == 11 [pid = 1952] [id = 38] 14:42:15 INFO - --DOCSHELL 0EC17BD8 == 10 [pid = 1952] [id = 37] 14:42:15 INFO - --DOCSHELL 0EAAB028 == 9 [pid = 1952] [id = 36] 14:42:15 INFO - --DOCSHELL 0C3D0608 == 8 [pid = 1952] [id = 35] 14:42:15 INFO - ###!!! ABORT: CRT ERROR HEAP CORRUPTION DETECTED: after Normal block (#4700183) at 0x0ED070B8. 14:42:15 INFO - CRT detected that the application wrote to memory after end of heap buffer. 14:42:15 INFO - Hit MOZ_CRASH() at c:/builds/moz2_slave/m-aurora-w32-d-000000000000000/build/memory/mozalloc/mozalloc_abort.cpp:30 14:42:15 INFO - nsStringStats 14:42:15 INFO - => mAllocCount: 340234 14:42:15 INFO - => mReallocCount: 34842 14:42:15 INFO - => mFreeCount: 321227 -- LEAKED 19007 !!! 14:42:15 INFO - => mShareCount: 438827 14:42:15 INFO - => mAdoptCount: 27099 14:42:15 INFO - => mAdoptFreeCount: 27096 -- LEAKED 3 !!! 14:42:15 INFO - => Process ID: 1952, Thread ID: 2700 14:42:15 WARNING - TEST-UNEXPECTED-FAIL | /tests/dom/indexedDB/test/test_webapp_clearBrowserData_inproc_inproc.html | application terminated with exit code 2147483651 14:42:15 INFO - INFO | runtests.py | Application ran for: 0:01:54.434000 14:42:15 INFO - INFO | zombiecheck | Reading PID log: c:\docume~1\cltbld~1.t-x\locals~1\temp\tmpssxi6spidlog 14:42:15 INFO - ==> process 1952 launched child process 316 ("C:\slave\test\build\application\firefox\plugin-container.exe" --channel=1952.ea2f898.854959525 -greomni "C:\slave\test\build\application\firefox\omni.ja" -appomni "C:\slave\test\build\application\firefox\browser\omni.ja" -appdir "C:\slave\test\build\application\firefox\browser" - 1952 "\\.\pipe\gecko-crash-server-pipe.1952" tab) 14:42:15 INFO - ==> process 1952 launched child process 2744 ("C:\slave\test\build\application\firefox\plugin-container.exe" --channel=1952.c2c3bd8.1258014750 -greomni "C:\slave\test\build\application\firefox\omni.ja" -appomni "C:\slave\test\build\application\firefox\browser\omni.ja" -appdir "C:\slave\test\build\application\firefox\browser" - 1952 "\\.\pipe\gecko-crash-server-pipe.1952" tab) 14:42:22 WARNING - PROCESS-CRASH | /tests/dom/indexedDB/test/test_webapp_clearBrowserData_inproc_inproc.html | application crashed [@ mozalloc_abort(char const * const)] 14:42:22 INFO - Crash dump filename: c:\docume~1\cltbld~1.t-x\locals~1\temp\tmpgv0j1j\minidumps\6203c2b6-09ea-4a53-acf4-f1e020ce2395.dmp 14:42:22 INFO - Operating system: Windows NT 14:42:22 INFO - 5.1.2600 Service Pack 3 14:42:22 INFO - CPU: x86 14:42:22 INFO - GenuineIntel family 6 model 30 stepping 5 14:42:22 INFO - 8 CPUs 14:42:22 INFO - Crash reason: EXCEPTION_BREAKPOINT 14:42:22 INFO - Crash address: 0x1371245 14:42:22 INFO - Thread 6 (crashed) 14:42:22 INFO - 0 mozalloc.dll!mozalloc_abort(char const * const) [mozalloc_abort.cpp:1a55393434e0 : 30 + 0x2c] 14:42:22 INFO - eip = 0x01371245 esp = 0x049eac94 ebp = 0x049eac9c ebx = 0x10319080 14:42:22 INFO - esi = 0x10261440 edi = 0x10260670 eax = 0x00000000 ecx = 0x5edb8e85 14:42:22 INFO - edx = 0x10361f48 efl = 0x00000212 14:42:22 INFO - Found by: given as instruction pointer in context 14:42:22 INFO - 1 xul.dll!MSCRTReportHook [nsAppRunner.cpp:1a55393434e0 : 1413 + 0x8] 14:42:22 INFO - eip = 0x03180120 esp = 0x049eaca4 ebp = 0x049eaca8 14:42:22 INFO - Found by: call frame info 14:42:22 INFO - 2 MSVCR100D.dll + 0x11b2a7 14:42:22 INFO - eip = 0x1031b2a8 esp = 0x049eacb0 ebp = 0x049efd34 14:42:22 INFO - Found by: call frame info 14:42:22 INFO - 3 MSVCR100D.dll + 0x120a31 14:42:22 INFO - eip = 0x10320a32 esp = 0x049efd3c ebp = 0x049efd54 14:42:22 INFO - Found by: previous frame's frame pointer 14:42:22 INFO - 4 MSVCR100D.dll + 0x1209ea 14:42:22 INFO - eip = 0x103209eb esp = 0x049efd5c ebp = 0x049efd7c 14:42:22 INFO - Found by: previous frame's frame pointer 14:42:22 INFO - 5 MSVCR100D.dll + 0x116cc2 14:42:22 INFO - eip = 0x10316cc3 esp = 0x049efd84 ebp = 0x049efda8 14:42:22 INFO - Found by: previous frame's frame pointer 14:42:22 INFO - 6 MSVCR100D.dll + 0x11696f 14:42:22 INFO - eip = 0x10316970 esp = 0x049efdb0 ebp = 0x049efde0 14:42:22 INFO - Found by: previous frame's frame pointer 14:42:22 INFO - 7 MSVCR100D.dll + 0x11908f 14:42:22 INFO - eip = 0x10319090 esp = 0x049efde8 ebp = 0x049efdf0 14:42:22 INFO - Found by: previous frame's frame pointer 14:42:22 INFO - 8 mozjs.dll!JSObject::finish(js::FreeOp *) [jsobjinlines.h:1a55393434e0 : 516 + 0x17] 14:42:22 INFO - eip = 0x00f6bb80 esp = 0x049efdf8 ebp = 0x049efe08 14:42:22 INFO - Found by: previous frame's frame pointer 14:42:22 INFO - 9 mozjs.dll!JSObject::finalize(js::FreeOp *) [jsobjinlines.h:1a55393434e0 : 103 + 0x7]
This looks more like a JS problem, but I can't tell for sure.
Group: core-security
Component: DOM: IndexedDB → JavaScript Engine
Naveed, can someone in JS look at this?
status-firefox29: --- → affected
tracking-firefox29: --- → +
Flags: needinfo?(nihsanullah)
cc-ing gc folks.
Naveed, any progress on this?
Assigning to Naveed to make sure someone has this bug assigned.
Assignee: nobody → nihsanullah
Hi Sylvestre, If you need to get an answer from Naveed, and needinfo? isn't working, please pick up the phone and call him. Assigning the bug to him is not going to help get anything done. Is this particular bug extra important for some reason? How often does this happen? This kind of report usually is not very actionable, and it would be quite hard to make it actionable---it would involve running the tests in a record-and-replay environment.
Assignee: nihsanullah → nobody
Has this happened again since? If it's just the once let's WFM and move on.
There are about a half-dozen intermittent failures with "CRT ERROR HEAP CORRUPTION DETECTED" in them, that have happened once or, in one case, twice.
This happened once on Aurora, a month and a half ago, so I blame gremlins.
Group: core-security
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(nihsanullah)
You need to log in before you can comment on or make changes to this bug.