Closed Bug 761384 Opened 12 years ago Closed 6 years ago

gecko crashes during Marionette tests on x86 emulator

Categories

(Firefox OS Graveyard :: Emulator, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jgriffin, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [b2g-crash])

Gecko crashes intermittently while running Marionette tests on the x86-emulator, but only on some systems.  It does not crash on the arm-emulator.

When the crash occurs, logcat shows a line similar to the following:

F/libc    (  807): Fatal signal 11 (SIGSEGV) at 0x0000000d (code=1)
I/DEBUG   (  795): debuggerd committing suicide to free the zombie!

This crash occurs at various times, and the address and code given are not always the same.

I noticed this about 75% of the time on Ubuntu 11.04; I've only seen it once since upgrading to 11.10.  It happens at nearly 100% on the Amazon VM we use to run webapi and other tests, so we've switched to using the arm emulator for testing instead.  The Amazon VM runs a custom linux distro which is based off of RHEL.

James Lal also mentioned the x86-emulator was misbehaving on the Linode VM running Ubuntu - not starting successfully - but that may or may not be a separate problem.

Also see bug 759822.

It would be great to get a stack trace for this, but I have no idea how to do that in B2G.
FWIW, I was able to "successfully" build the x86 (and arm) emulators on a standalone Ubuntu 12.04 machine, after symlinking libGL and libX11 to the expected spots, which suggests James' problem may be local to the linode.

I put "successfully" in quotes because the multi-emulator tests did not work with the x86 emulator I built. However, that was also true of the x86 emulators that were prebuilt and given to us, so I think my build was about as good as one would expect.
Keywords: crash
Whiteboard: [b2g-crash]
Component: General → Emulator
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.