Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

latest build crashes after a few seconds #362

Closed
cadeyrn opened this issue Dec 27, 2018 · 5 comments
Closed

latest build crashes after a few seconds #362

cadeyrn opened this issue Dec 27, 2018 · 5 comments

Comments

@cadeyrn
Copy link

cadeyrn commented Dec 27, 2018

After today's changes I updated my reference browser. When I start the reference browser it crashes after a few seconds.

Latest messages from logcat:

2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: Build fingerprint: 'htc/ocndugl_00401/htc_ocndugl:8.0.0/OPR6.170623.013/1002308.19:user/release-keys'
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: Revision: '0'
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: ABI: 'arm'
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: pid: 24428, tid: 24447, name: Gecko >>> org.mozilla.reference.browser.debug:tab <<<
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: Cause: null pointer dereference
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: r0 00000000 r1 00005f7f r2 0000000b r3 ea278c90
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: r4 f58aa8a1 r5 00005fca r6 00000001 r7 0000016b
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: r8 00000000 r9 e18199c8 sl 00000016 fp 0000000b
2018-12-27 19:25:58.074 24525-24525/? A/DEBUG: ip ea278ad0 sp ea278ac0 lr eca641c7 pc ecaa6e1c cpsr 00000010
2018-12-27 19:25:58.076 24525-24525/? A/DEBUG: backtrace:
2018-12-27 19:25:58.076 24525-24525/? A/DEBUG: #00 pc 0005be1c /system/bin/linker (__dl_syscall+32)
2018-12-27 19:25:58.076 24525-24525/? A/DEBUG: #1 pc 000191c3 /system/bin/linker (__dl__ZL13resend_signalP7siginfob+54)
2018-12-27 19:25:58.076 24525-24525/? A/DEBUG: #2 pc 0001901f /system/bin/linker (__dl__ZL24debuggerd_signal_handleriP7siginfoPv+710)
2018-12-27 19:25:58.076 24525-24525/? A/DEBUG: #3 pc 021df479 /data/app/org.mozilla.reference.browser.debug-jKPbQwTHsgrU1Z-agxUQng==/lib/arm/libxul.so (offset 0x13b000)
2018-12-27 19:25:58.340 2019-2019/? E/NetworkController: GSM STATE_IN_SERVICE mESimEnable = false, slot 0
2018-12-27 19:25:58.543 1253-1253/? E//system/bin/tombstoned: Tombstone written to: /data/tombstones//tombstone_00
2018-12-27 19:25:58.545 1736-24526/? E/ActivityManager: App crashed! Process: org.mozilla.reference.browser.debug:tab

HTC U11
Android 8.0.0

(I am not sure which build was my previous so I still have to check which change caused the crash)

@cadeyrn
Copy link
Author

cadeyrn commented Dec 27, 2018

The crash happens since the GeckoView update from version 65.0.20181129095546 to 66.0.20181217093726 in 28283d2.

@jonalmeida
Copy link
Collaborator

jonalmeida commented Dec 27, 2018

@cadeyrn by any chance, do you happen to know which current tab is open?

EDIT: or any steps to reproduce? :) We're trying to reproduce the issue here, but everything seems fine. We're wondering what current state your browser is in now and what it was in before you updated?

@cadeyrn
Copy link
Author

cadeyrn commented Dec 27, 2018

The current tab is https://www.mozilla.org/en-US/. My only step was to checkout a revision from GitHub, compile with Android Studio and run the app.

I don't know why but I changed the revision several times and it always crashed with 28283d2 or newer and never with older revisions. But now there is no longer a crash with the latest revision. The only thing I did was to restart Android Studio.

@jonalmeida
Copy link
Collaborator

Restarting Android Studio would have called gradle sync ('Sync Project with Gradle Files') which would have pulled in the any updated dependencies instead of using the last cached ones. My guess is, that was the issue. :)

We can leave this issue open for a bit if you think you might be able to reproduce the issue, otherwise feel free to close it.

@cadeyrn
Copy link
Author

cadeyrn commented Dec 28, 2018

Since I can no longer reproduce let's close the issue. If it happens again, it can still be reopenend. :)

@cadeyrn cadeyrn closed this as completed Dec 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants