1356595 - crash not sent

Status: RESOLVED DUPLICATE of bug 1041968

(Firefox for Android Graveyard :: General, defect)

Description

[Lazy Monkey]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170414030225

Steps to reproduce:

I was simply browsing


Actual results:

fennec suddenly closed while browsing. I think it crashed. 
in the logcat I see this:
04-14 16:47:06.554   822  1380 I ActivityManager: Process org.mozilla.fennec (pid 8040) has died.

04-14 16:47:06.554   822  1357 I WindowState: WIN DEATH: Window{41b336e0 u0 org.mozilla.fennec/org.mozilla.gecko.BrowserApp}

04-14 16:47:06.554   822  1357 W WindowManager: Force-removing child win Window{41b61128 u0 SurfaceView} from container Window{41b336e0 u0 org.mozilla.fennec/org.mozilla.gecko.BrowserApp}

04-14 16:47:06.554   822  1380 W ActivityManager: Scheduling restart of crashed service org.mozilla.fennec/org.mozilla.gecko.media.MediaControlService in 1000ms

04-14 16:47:06.844   822  1380 W ActivityManager: Force removing ActivityRecord{4197ef48 u0 org.mozilla.fennec/org.mozilla.gecko.BrowserApp t504}: app died, no saved state

after the crash I reloaded fennec and went into about:crashes expecting to see the log for the crash, but it was emtpy. it seems that the crash data was not sent to mozilla.


Expected results:

crash data should appear in about:crashes, and should be sent to mozilla.

Comment 1

[Jan Henning [:JanH]]

Does the logcat contain anything about the actual crash itself?

Comment 2

[Lazy Monkey]

I have not found any information about the specific error.
I remember that just before the crash I openened the firefox menu, because I wanted to share a link.
I'm not sure but I think I have seen for a second the menu with some strange text menu items, then firefox closed abruptly.

Comment 3

[Lazy Monkey]

Hi, I got another crash while opening the firefox menu (using the capacitive button on the phone, not the "three point button" at top right in firefox ui. And the crash is not recorded in about:crashes just like the previous one I reported. 
I'm not sure if the crash data is sent to mozilla but not saved locally, or it is not sent at all.

Here is the log:

04-21 10:24:04.805 25458 30932 I FxAccounts: fennec :: GlobalSession :: Running next stage completed (org.mozilla.gecko.sync.stage.CompletedStage@41f34f88)...

04-21 10:24:04.805 25458 30932 I FxAccounts: fennec :: FxAccountSyncAdapter :: Global session succeeded.

04-21 10:24:04.815 25458 30932 I FxAccounts: fennec :: FxAccountSchedulePolicy :: Scheduling periodic sync for 43200.

04-21 10:24:04.845 25458 30932 I FxAccounts: fennec :: FxAccountSyncAdapter :: Sync succeeded.

04-21 10:24:04.845 25458 30896 I FxAccounts: fennec :: FxAccountSyncAdapter :: Syncing done.

04-21 10:24:58.885   822  1347 I ActivityManager: Process org.mozilla.fennec (pid 25458) has died.

04-21 10:24:58.885   822  3504 I WindowState: WIN DEATH: Window{43817030 u0 org.mozilla.fennec/org.mozilla.gecko.BrowserApp}

04-21 10:24:58.885   822  3504 W WindowManager: Force-removing child win Window{41d1d528 u0 PopupWindow:42002ee8} from container Window{43817030 u0 org.mozilla.fennec/org.mozilla.gecko.BrowserApp}

04-21 10:24:58.895   822  1347 W ActivityManager: Scheduling restart of crashed service org.mozilla.fennec/org.mozilla.gecko.media.MediaControlService in 1000ms

04-21 10:24:58.895   822  1347 W ActivityManager: Force removing ActivityRecord{41ab7ae8 u0 org.mozilla.fennec/org.mozilla.gecko.BrowserApp t938}: app died, no saved state

04-21 10:24:59.145   822  3504 W WindowManager: Force-removing child win Window{4399e810 u0 SurfaceView} from container Window{43817030 u0 org.mozilla.fennec/org.mozilla.gecko.BrowserApp}

04-21 10:25:00.835  1348  1348 I Timeline: Timeline: Activity_launch_request id:org.mozilla.fennec time:240163749

04-21 10:25:00.845   822   833 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.mozilla.fennec/.App bnds=[0,722][216,1047] (has extras)} from pid 1348

04-21 10:25:01.185   822  1380 I ActivityManager: Start proc org.mozilla.fennec for activity org.mozilla.fennec/.App: pid=31137 uid=10202 gids={50202, 3003, 1028, 1015, 1006}

04-21 10:25:01.235 31137 31137 D ActivityThread: handleBindApplication:org.mozilla.fennec

04-21 10:25:01.315 31137 31137 I Timeline: Timeline: Activity_launch_request id:org.mozilla.fennec time:240164221

04-21 10:25:01.315   822 11173 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x200000 cmp=org.mozilla.fennec/org.mozilla.gecko.BrowserApp bnds=[0,722][216,1047] (has extras)} from pid 31137

04-21 10:25:01.345 31137 31137 D dalvikvm: Trying to load lib /data/app-lib/org.mozilla.fennec-1/libmozglue.so 0x41910768

<cut>

Comment 4

[Jan Henning [:JanH]]

Hm, maybe I've misremembered or it changed, but it seems like we don't log crash stacks if the crash reporter is enabled for a build, so the lack of info there might be expected.

To clarify: Did the crash reporter run, or did Firefox simply crash and disappear from the screen? Also, which Firefox version and device (model, Android version)?

Comment 5

[Lazy Monkey]

Hello,
I didn't see the crash report. Firefox died unexpectedly, and then restarted very fast.
The Firefox is Nightly 55. The last report is from the 20/04 build, the first one I don't remember.
The device is a Oneplus One phone, running Android 4.4.4

Comment 6

[Sorina Florean [:sflorean]]

Maybe dupe of bug 1041968?