zhanghai / zhanghai/MaterialFiles

crashes at start after being installed for a few hours

Open
#882 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
9k
Forks
736
PR merge metrics
No merged PRs in 30d

Description

Hi,
The app won't start after a few hours of being installed. If I uninstall and reinstall, it works again until the day after.

Here is what I get from adb logcat -e me.zhanghai.android.files on Android 8.1.0:

11-06 18:44:33.675  2480  5320 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=me.zhanghai.android.files/.filelist.FileListActivity} from uid 10022
11-06 18:44:33.682   581   581 E ANDR-IOP: IOP HAL: Received pkg_name = me.zhanghai.android.files pid = -1
11-06 18:44:33.687  2480  5320 D ActivityTrigger: activityStartTrigger: Activity is Triggerred in full screen ApplicationInfo{5f72fe0 me.zhanghai.android.files}
11-06 18:44:33.687  2480  5320 E ActivityTrigger: activityStartTrigger: not whiteListedme.zhanghai.android.files/me.zhanghai.android.files.filelist.FileListActivity/31
11-06 18:44:33.688  2480  5320 D ActivityTrigger: activityResumeTrigger: The activity in ApplicationInfo{5f72fe0 me.zhanghai.android.files} is now in focus and seems to be in full-screen mode
11-06 18:44:33.688  2480  5320 E ActivityTrigger: activityResumeTrigger: not whiteListedme.zhanghai.android.files/me.zhanghai.android.files.filelist.FileListActivity/31
11-06 18:44:33.693  3922 32548 D b       : Bundle[{quick_action=false, source=Desktop, type=launched_activity, serial_number=0, component_name=me.zhanghai.android.files/me.zhanghai.android.files.filelist.FileListActivity}]
11-06 18:44:33.696  2480  2607 D ActivityTrigger: activityResumeTrigger: The activity in ApplicationInfo{5f72fe0 me.zhanghai.android.files} is now in focus and seems to be in full-screen mode
11-06 18:44:33.696  2480  2607 E ActivityTrigger: activityResumeTrigger: not whiteListedme.zhanghai.android.files/me.zhanghai.android.files.filelist.FileListActivity/31
11-06 18:44:33.697  2105  2105 I zygoteman: zygote_per64: launch 2160 (no limit) (me.zhanghai.android.files)
11-06 18:44:33.710  2105  2105 I zygoteman: PERF: Launched 'me.zhanghai.android.files' (pid=32558) in 12 ms
11-06 18:44:33.710  2105  2105 I zygoteman: me.zhanghai.android.files launch complete
11-06 18:44:33.710  2480  2607 I ActivityManager: Start proc 32558:me.zhanghai.android.files/u0a319 for activity me.zhanghai.android.files/.filelist.FileListActivity
11-06 18:44:33.840 32558 32558 F zygote64: runtime.cc:523] #20 pc 00000000001cc52c  /data/app/me.zhanghai.android.files-8D7e8cCUOfRJ5s7T0oceIQ==/oat/arm64/base.odex (???)
11-06 18:44:33.895 32577 32577 F DEBUG   : pid: 32558, tid: 32558, name: i.android.files  >>> me.zhanghai.android.files <<<
11-06 18:44:33.907 32577 32577 F DEBUG   :     #19 pc 00000000002f352c  /data/app/me.zhanghai.android.files-8D7e8cCUOfRJ5s7T0oceIQ==/oat/arm64/base.odex (offset 0x127000)
11-06 18:44:34.570  2480 32578 W ActivityManager:   Force finishing activity me.zhanghai.android.files/.filelist.FileListActivity
11-06 18:44:34.576  2480  2561 E BootReceiver: try to find package for process: me.zhanghai.android.files
11-06 18:44:34.579  2480  2561 E BootReceiver: Found a package for process: me.zhanghai.android.files -> me.zhanghai.android.files
11-06 18:44:34.594  2105  2105 I zygoteman: App me.zhanghai.android.files terminated, pid=32558
11-06 18:44:34.594  2480  2607 I ActivityManager: Process me.zhanghai.android.files (pid 32558) has died: vis  +99TOP 

And with adb logcat --buffer=crash:

11-06 18:52:13.595  1240  1240 F libc    : Fatal signal 6 (SIGABRT), code -6 in tid 1240 (i.android.files), pid 1240 (i.android.files)
11-06 18:52:13.661  1259  1259 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-06 18:52:13.661  1259  1259 F DEBUG   : Build fingerprint: 'blackberry/bbb100emea/bbb100:8.1.0/OPM1.171019.026/ABS154:user/release-keys'
11-06 18:52:13.661  1259  1259 F DEBUG   : Revision: '0'
11-06 18:52:13.661  1259  1259 F DEBUG   : ABI: 'arm64'
11-06 18:52:13.661  1259  1259 F DEBUG   : pid: 1240, tid: 1240, name: i.android.files  >>> me.zhanghai.android.files <<<
11-06 18:52:13.661  1259  1259 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-06 18:52:13.664  1259  1259 F DEBUG   : Abort message: 'entrypoint_utils-inl.h:97] Could not find an inlined method from an .oat file: the class Landroidx/activity/c; was not found in the class loader of void org.bouncycastle.jce.provider.BouncyCastleProvider.loadAlgorithms(java.lang.String, java.lang.String[]). This must be due to playing wrongly with class loaders'
11-06 18:52:13.664  1259  1259 F DEBUG   :     x0   0000000000000000  x1   00000000000004d8  x2   0000000000000006  x3   0000000000000008
11-06 18:52:13.664  1259  1259 F DEBUG   :     x4   0000000000000000  x5   0000000000000000  x6   0000000000000000  x7   0080808080808080
11-06 18:52:13.664  1259  1259 F DEBUG   :     x8   0000000000000083  x9   71e289372ad5ffa5  x10  0000000000000000  x11  0000000000000001
11-06 18:52:13.664  1259  1259 F DEBUG   :     x12  ffffffffffffffff  x13  0000000000000008  x14  ffffffffffffffff  x15  00008b6ec89470e3
11-06 18:52:13.664  1259  1259 F DEBUG   :     x16  000000108a87afa8  x17  00000043939047d8  x18  0000000000000008  x19  00000000000004d8
11-06 18:52:13.664  1259  1259 F DEBUG   :     x20  00000000000004d8  x21  0000000000000002  x22  0000004394bbda40  x23  0000005193cea209
11-06 18:52:13.664  1259  1259 F DEBUG   :     x24  0000000000000010  x25  0000000000000021  x26  000000000000011d  x27  000000000000033b
11-06 18:52:13.664  1259  1259 F DEBUG   :     x28  000000430fea80c0  x29  0000005193cea1b0  x30  00000043938ba038
11-06 18:52:13.664  1259  1259 F DEBUG   :     sp   0000005193cea170  pc   00000043938ba054  pstate 0000000060000000
11-06 18:52:13.674  1259  1259 F DEBUG   : 
11-06 18:52:13.674  1259  1259 F DEBUG   : backtrace:
11-06 18:52:13.675  1259  1259 F DEBUG   :     #00 pc 000000000001e054  /system/lib64/libc.so (abort+104)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #01 pc 000000000047187c  /system/lib64/libart.so (art::Runtime::Abort(char const*)+552)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #02 pc 0000000000566ddc  /system/lib64/libart.so (android::base::LogMessage::~LogMessage()+996)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #03 pc 000000000048a3f4  /system/lib64/libart.so (art::GetResolvedMethod(art::ArtMethod*, art::MethodInfo const&, art::InlineInfo const&, art::InlineInfoEncoding const&, unsigned char)+2292)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #04 pc 0000000000488ac8  /system/lib64/libart.so (art::StackVisitor::GetMethod() const+544)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #05 pc 00000000004a5eac  /system/lib64/libart.so (art::CurrentMethodVisitor::VisitFrame()+16)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #06 pc 0000000000487b50  /system/lib64/libart.so (_ZN3art12StackVisitor9WalkStackILNS0_16CountTransitionsE0EEEvb+1088)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #07 pc 000000000049891c  /system/lib64/libart.so (art::Thread::DumpStack(std::__1::basic_ostream<char, std::__1::char_traits<char>>&, bool, BacktraceMap*, bool) const+316)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #08 pc 00000000004b04d0  /system/lib64/libart.so (art::DumpCheckpoint::Run(art::Thread*)+884)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #09 pc 00000000004a8d74  /system/lib64/libart.so (art::ThreadList::RunCheckpoint(art::Closure*, art::Closure*)+480)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #10 pc 00000000004a8518  /system/lib64/libart.so (art::ThreadList::Dump(std::__1::basic_ostream<char, std::__1::char_traits<char>>&, bool)+288)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #11 pc 000000000047ffac  /system/lib64/libart.so (art::AbortState::Dump(std::__1::basic_ostream<char, std::__1::char_traits<char>>&) const+220)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #12 pc 0000000000471718  /system/lib64/libart.so (art::Runtime::Abort(char const*)+196)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #13 pc 0000000000566ddc  /system/lib64/libart.so (android::base::LogMessage::~LogMessage()+996)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #14 pc 000000000048a3f4  /system/lib64/libart.so (art::GetResolvedMethod(art::ArtMethod*, art::MethodInfo const&, art::InlineInfo const&, art::InlineInfoEncoding const&, unsigned char)+2292)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #15 pc 0000000000503904  /system/lib64/libart.so (art::DoGetCalleeSaveMethodCaller(art::ArtMethod*, unsigned long, bool)+668)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #16 pc 0000000000503d74  /system/lib64/libart.so (art::GetCalleeSaveMethodCallerAndOuterMethod(art::Thread*, art::CalleeSaveType)+152)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #17 pc 000000000051607c  /system/lib64/libart.so (artInitializeTypeFromCode+32)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #18 pc 00000000005472a8  /system/lib64/libart.so (art_quick_initialize_type+168)
11-06 18:52:13.675  1259  1259 F DEBUG   :     #19 pc 00000000002f352c  /data/app/me.zhanghai.android.files-8D7e8cCUOfRJ5s7T0oceIQ==/oat/arm64/base.odex (offset 0x127000)

I'm a newbee on Android so let me know if there's a better way to get logs.

Thank you for the work, the app is great!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the FileListActivity launch shown in the adb logcat output and inspect the crash details from adb logcat --buffer=crash, especially the Android 8.1 ART and BouncyCastle class-loader message. Reproduce the delayed startup failure and confirm that the app launches successfully after remaining installed for several hours.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.