Closed Bug 575570 Opened 14 years ago Closed 14 years ago

Random reftest crash during shutdown [@ arena_dalloc_small] [@ arena_purge] indicating prior memory corruption

Categories

(Testing :: Reftest, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: hsivonen, Unassigned)

References

()

Details

(Keywords: intermittent-failure)

REFTEST INFO | Successful: 4445 (4427 pass, 18 load only)
REFTEST INFO | Unexpected: 0 (0 unexpected fail, 0 unexpected pass, 0 unexpected asserts, 0 unexpected fixed asserts, 0 failed load, 0 exception)
REFTEST INFO | Known problems: 236 (181 known fail, 0 known asserts, 37 random, 18 skipped)
REFTEST INFO | Total canvas count = 14
REFTEST TEST-START | Shutdown
NEXT ERROR TEST-UNEXPECTED-FAIL | Shutdown | Exited with code -1073741819 during test run
INFO | automation.py | Application ran for: 0:13:43.361000

The push was http://hg.mozilla.org/mozilla-central/rev/3642a4a60851 , so it seems extremely unlikely that the push could have caused this.
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1278014151.1278016381.28690.gz
Rev3 WINNT 6.1 mozilla-central opt test reftest on 2010/07/01 12:55:51
s: talos-r3-w7-030
Some of the crashes in these logs are at IntentionalCrash and some are at arena_* functions. I think the arena_* ones are all D2D, and IntentionalCrash ones are non-D2D.
Summary: Random failure at reftest shutdown: Shutdown | Exited with code -1073741819 during test run → Random reftest crash during shutdown [@ arena_dalloc_small] and other locations indicating prior memory corruption
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1279218645.1279219998.20656.gz#err0
Summary: Random reftest crash during shutdown [@ arena_dalloc_small] and other locations indicating prior memory corruption → Random reftest crash during shutdown [@ arena_dalloc_small] [@ arena_purge] indicating prior memory corruption
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.