Used Mark Finkle's geckobrowser library [1] to exercise GeckoView with the latest nightly [2]. The apk crashed on launch with stack traces attached. GeckoView should have rendered the given URL. This last worked with [3] [1] https://github.com/mfinkle/geckobrowser [2] http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2014-07-01-03-02-02-mozilla-central-android/ [3] http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2014-06-09-03-02-02-mozilla-central-android/

This occurs on a Nexus5 running Android 4.4.4.

The latest version still works for me on: * Nexus 5 running 4.4.4 * Galaxy Nexus running 4.3 In you logcat I see: D/GeckoAppShell(462): Killing via System.exit() Which I think means Gecko is shutting down for some reason. Called from: http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/GeckoAppShell.java#779 http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/nsAndroidStartup.cpp#78 Which is why we see: I/fennec(462): XRE_main returned 1 But why Gecko is shutting down, I don't know.

What devices are you testing with? I have a Moto G (4.4.2) and two Galaxy Nexuses (4.0.4 and 4.1.2). I'll test with those are report back. Are there any environment variables I can set to turn on more logging? Do I just need to build from source and then add printfs?

Sorry, I didn't see Comment #2 when I posted. Would it help for me to attach the source for my projects?

(In reply to Heath Borders from comment #4) > Sorry, I didn't see Comment #2 when I posted. > > Would it help for me to attach the source for my projects? If you have a small testcase, that would be fine. Just zip it up and attach it here.

(In reply to Mark Finkle (:mfinkle) from comment #5) > (In reply to Heath Borders from comment #4) > > Sorry, I didn't see Comment #2 when I posted. > > > > Would it help for me to attach the source for my projects? > > If you have a small testcase, that would be fine. Just zip it up and attach > it here. Or post the repo details.

Mass change of bugs in the "Embedding: GRE Core" component in preparation for archiving it. I believe that these are no longer relevant; but if they are, they should be reopened and moved into a component relevant to the code in question.

Moving to Core::Embedding: APIs, where we'll continue to triage and track GeckoView issues, but leaving this resolved incomplete, since the reporter didn't end up providing a test case. Please reopen if you have steps and code to reproduce!