Scoop sometimes crashes when capturing traceback

[jrabinow]

An app crashed while I was using it. Almost immediately I got a scoop notification, but it was a scoop crash, not a crash for the app I was using.

Given the timing, I'm assuming scoop crashed when trying to capture a traceback for the other app.

This has happened twice in the last 6h, I switched from the old xposed repo version to the fdroid app just yesterday. Speaking of which, many thanks for maintaining scoop, I was glad to see someone had adopted it.

java.lang.IllegalArgumentException: fromIndex(1) > toIndex(0)
	at java.util.ArrayList.subListRangeCheck(ArrayList.java:1018)
	at java.util.ArrayList.subList(ArrayList.java:1008)
	at taco.scoop.core.service.detector.CrashDetector.reportCrash(CrashDetector.kt:64)
	at taco.scoop.core.service.detector.CrashDetector.access$reportCrash(CrashDetector.kt:11)
	at taco.scoop.core.service.detector.CrashDetector$readThread$1.run(CrashDetector.kt:29)

[TacoTheDank]

🤔 Interesting, I haven't seen anyone experience something like this before...

I was glad to see someone had adopted it.

You are most welcome! I had been using an improved forked version for about two years before I decided to upgrade it as it was looking shabby :)

[TacoTheDank]

@jrabinow What Xposed system are you using? Are you still using the old Xposed, or have you updated to something like EdExposed, LSPosed, or something like that? Or, are you not using Xposed and simply relying on the root permission instead? Also, what Android version? Might not be related, but just in case.

[jrabinow]

I'm on EdXposed but I haven't rebooted to activate the module yet, so right now things should be working in root-only mode. I'm running android 10

[jrabinow]

I should also mention, there's one possibility which could be nasty for users, where scoop crashes while collecting its own stack trace, and produces a stack trace while doing so, which then goes on to be collected by scoop, which crashes again and so on. This could lead to an infinite crash loop of sorts
Thankfully this isn't happening here… could this scenario happen? Could anything be done to prevent it?

[jrabinow]

I rebooted and have been using the xposed module since 2 days after this issue was created. I just got the same crash twice in a row

[quantenzitrone]

i think i just had the same problem
some saved stacktrace seemed to crash scoop every time i do anything other than being in the crash log overview, so

• when i click on any stacktrace to view it (and copy it)
• when i go to the settings
• when i leave the app

I don't know which stacktrace it was, and i wouldn't be able to send it to you anyway, because scoop wouldn't let me view the traces.
Anyway, I cleared all saved traces, and now it seems to work again.

My phone is a SHIFT6m with a custom ungoogled ROM by the manufacturer with Magisk Root.

[TacoTheDank]

@quantenzitrone That sounds like #45.

[quantenzitrone]

yeah thats sounds more like it
i probably had a large number of crashes too