777751 - Intermittent crash in crashtests/382899-1.xul | Exited with code -6 during test run ("firefox-bin(349,0x7fff70cc9cc0) malloc: *** error for object 0x128ab5f48: incorrect checksum for freed object - object was probably modified after being freed.")

Status: RESOLVED INVALID

(Core :: XPCOM, defect)

Description

[Ed Morley [:emorley]]

Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound debug test crashtest on 2012-07-26 07:32:06 PDT for push 2b0e4574d8d0

slave: talos-r4-snow-014

https://tbpl.mozilla.org/php/getParsedLog.php?id=13875102&tree=Mozilla-Inbound

{
REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/xul/base/src/crashtests/382899-1.xul | 1833 / 2099 (87%)
++DOMWINDOW == 40 (0x128a67330) [serial = 4182] [outer = 0x1085e5dc0]
firefox-bin(349,0x7fff70cc9cc0) malloc: *** error for object 0x128ab5f48: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
WARNING: shutting down early because of crash!: file ../../../../dom/plugins/ipc/PluginModuleChild.cpp, line 703
WARNING: plugin process _exit()ing: file ../../../../dom/plugins/ipc/PluginModuleChild.cpp, line 668
TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/xul/base/src/crashtests/382899-1.xul | Exited with code -6 during test run
INFO | automation.py | Application ran for: 0:05:32.290386
INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpdUhEqppidlog
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | missing output line for total leaks!
TEST-UNEXPECTED-FAIL | plugin process 353 | automationutils.processLeakLog() | missing output line for total leaks!
}

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

In bug 785724 I requested that talos-r4-snow-014 be removed from service due to memory corruption problems.

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

This bug was observed only on one or more of the six machines listed in
bug 787281 comment 11, which seem likely to have bad memory, disk, or
other hardware problem, based on the rate of failures on those machines
and the types of failures observed.

Therefore I'm marking this bug invalid, though it should be reopened if
it occurs on other (more reliable) hardware.