1241166 - DMD eventually crashes when running sequential torture mode in emunittest suite.

Status: NEW

(Core :: DMD, defect)

Description

[Jukka Jylänki]

STR:

1. Build Firefox with DMD enabled.
2. Run the emunittest 0.5 suite in "Run all tests" mode with "sequential torture mode" enabled.

After a while, Firefox content process will crash in dmd.dll, e.g. https://crash-stats.mozilla.com/report/index/639d2a2b-fa73-4e78-b907-53c992160120

Please contact me directly to obtain the emunittest suite.

Comment 1

[Nicholas Nethercote [inactive]]

The crash has no source file/line info. Is it possible to get a crash that does have that info?

Comment 2

[Jukka Jylänki]

I'm not sure why it doesn't have that info and what one has to do to add it. I'll see if I can get the crash again to see if it would report anything better.

Comment 3

[Andrew McCreight [:mccr8]]

It isn't including that info because you probably used a local build, so there are no symbols for it on crash-stats. You could try running the tests under a debugger. That might give you a better stack trace when it crashes.

Comment 4

[Jukka Jylänki]

Attachment: crash_callstack.png

Disabled e10s and started Firefox with MOZ_CRASHREPORTER_DISABLE=1, and ran it attached to Visual Studio. Running emunittest suite repeatedly eventually crashed in DMD as shown in this callstack.

Comment 5

[Jukka Jylänki]

Attachment: crash_callstack2.png

Stack of the parent function looks like this.

Comment 6

[Jukka Jylänki]

Attachment: crash_callstack3.png

And the parent of that function.

Assuming that Visual Studio debugger interpretation is correct, then gLiveBlockTable->lookup() returned an object p, for which p->Report() has a bogus this pointer, which would indicate that the LiveBlockTable::Ptr p that was returned was bogus. Not sure for certain though.

Comment 7

[Jukka Jylänki]

Interestingly the crash occurred when loading Dead Trigger 2 in the suite, which is available also at http://beta.unity3d.com/jonas/DT2/, and the first time the crash occurred, it was also during loading Dead Trigger 2, and on both runs, it occurred on the second run-through of the suite, so first Dead Trigger 2 load succeeded ok.