Closed
Bug 966990
Opened 11 years ago
Closed 9 years ago
Intermittent b2g xpcshell debug | Assertion failure: data, at ../../../gecko/xpcom/base/nsCycleCollector.cpp:3615
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: ahal, Unassigned)
References
Details
(Keywords: intermittent-failure)
Example:
https://tbpl.mozilla.org/php/getParsedLog.php?id=33989315&tree=Mozilla-Inbound#error0
This seems to be affecting the opt builds too:
https://tbpl.mozilla.org/php/getParsedLog.php?id=33995417&tree=Mozilla-Inbound#error0
We need a stack to do anything here. Something is calling this API too late or too early.
Flags: needinfo?(ahalberstadt)
Reporter | ||
Comment 2•11 years ago
|
||
In the debug log I see:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Android/full/generic:4.0.4.0.4.0.4/OPENMASTER/eng.cltbld.20140202.192004:eng/test-keys'
pid: 1036, tid: 1036 >>> /data/local/xpcb/xpcshell <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
r0 0000005d r1 be891338 r2 12951ae6 r3 0000007b
r4 440a5d08 r5 00000000 r6 00000000 r7 440a5d20
r8 be8917df r9 00000000 10 42905bd0 fp 0000000c
ip 40054108 sp be891788 lr 405c7eb7 pc 405c7eb8 cpsr 20000030
d0 3fedfffffffffffe d1 3ff0000000000000
d2 bebbbc8442152471 d3 3f1155f4621facbd
d4 bfb0b316b3c740df d5 4000000000000000
d6 0000000000000000 d7 0000000000000000
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
scr 20000011
#00 pc 00020eb8 /system/b2g/libxul.so
#01 lr 405c7eb7 /system/b2g/libxul.so
code around pc:
405c7e98 4a2b492a 44794b2b 447a482b 4478447b *I+J+KyD+HzD{DxD
405c7ea8 f6409000 900130f5 f7df2007 237beab0 ..@..0... ....{#
405c7eb8 e7e4602b 4380f508 9094f8d3 0f00f1b9 +`.....C........
405c7ec8 f44fd110 f3d74080 4605ede4 9000f8c0 ..O..@.....F....
405c7ed8 f1084629 f7fc0090 f8d8fcfb 602b3094 )F...........0+`
code around lr:
405c7e94 b98d9d03 4a2b492a 44794b2b 447a482b ....*I+J+KyD+HzD
405c7ea4 4478447b f6409000 900130f5 f7df2007 {DxD..@..0... ..
405c7eb4 237beab0 e7e4602b 4380f508 9094f8d3 ..{#+`.....C....
405c7ec4 0f00f1b9 f44fd110 f3d74080 4605ede4 ......O..@.....F
405c7ed4 9000f8c0 f1084629 f7fc0090 f8d8fcfb ....)F..........
stack:
be891748 40205280
be89174c 4027e880
be891750 40205280
be891754 40299190
be891758 40205280
be89175c 44051460
be891760 4021e000
be891764 12951ae6
be891768 400c6040
be89176c 440a5d08
be891770 00000000
be891774 00000000
be891778 440a5d20
be89177c 405c7eb7 /system/b2g/libxul.so
be891780 df0027ad
be891784 00000000
#00 be891788 420291d0 /system/b2g/libxul.so
be89178c 00000e1f
be891790 429a4900
be891794 00001000
be891798 00000085
be89179c 00000001
be8917a0 00000002
be8917a4 440a5d20
be8917a8 440a5d20
be8917ac 00001000
be8917b0 00000000
be8917b4 40e0fb0d /system/b2g/libxul.so
be8917b8 440a5d20
be8917bc 440a5d08
be8917c0 4021f080
be8917c4 440a5d00
be8917c8 440a5d08
be8917cc 40e0fbd9 /system/b2g/libxul.so
Or are you looking for a minidump?
Flags: needinfo?(ahalberstadt)
That's not a useful stack ... we need symbols here
Reporter | ||
Comment 4•11 years ago
|
||
Reading the log, the problem seems to be that the harness isn't catching the timeout before the mozharness timeout is triggered (which doesn't check for minidumps). Looks like someone already filed bug 889317 for this.
Depends on: 889317
Updated•11 years ago
|
Keywords: intermittent-failure
Comment 5•9 years ago
|
||
Inactive; closing (see bug 1180138).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•