AntennaPod crash on Graphene OS due to native code debugging. #6993
Comments
benmordecai
added
the
Type: Possible bug
|
Do you get the same message if you open the description of a non-playing item? This sounds like something is wrong with Vandium WebView, not with AntennaPod. AntennaPod just displays the description using a WebView, so if that then makes the app crash, it is something outside the control of AntennaPod |
keunes
added
the
Needs: Reply
|
Graphene just pushed an update. I am going to play some episodes and see if the problem returns. It only ever happens during playback and often with the screen locked for > 5 mins |
|
Just for the sake of adding a data point, I use AntennaPod (from F-Droid) on GrapheneOS, also a Pixel 6a with up to date software and native code debugging blocked, and I can't reproduce this bug. I usually have the screen locked for long times during bike commute, like 30 minutes, and no issue. Maybe something else in your setup? I use AntennaPod in my main profile, if that can have an impact. |
|
This is definitely still an issue for me as it is still crashing several times per day. I have native code debugging allowed which is the default setting but it still generates a notification that says "Vandium System WebView tried to use native code debugging" every time that it crashes. It is possible that this message is merely a symptom of the crash and is actually irrelevant. @maaaat and I have the same hardware, OS, and AntennaPod source. I only use AntennaPod on my main profile which does not have Google Play services installed |
|
When this happens, does the time stamp on the "report bug" screen change and still has the same stack trace? If so, this is probably unrelated to Vanadium System WebView and simply the same as #7001 |
|
The latest stack trace shows 02-01-2024 which is not the same time as the latest crash. |
|
You say this started occurring a few days ago but the last AntennaPod update was a few months ago. Maybe Vanadium was updated then? Maybe you could try uninstalling the Vanadium updates? I'm still convinced that this is not actually an AntennaPod problem but a Vanadium problem. |
|
This is my current Vandium version: https://github.com/GrapheneOS/Vanadium/releases/tag/123.0.6312.40.0 As far as I know Graphene is rolling release with atomic updates and there is no way to rollback updates but I am not certain about this. Looking more closely at the 2-01-2024 date, I think this would predate the first occurrence of the crash and maybe this is a dummy stack trace unrelated to the crashes I am experiencing now. |
|
This issue will be closed when we don't get a reply within 7 days. |
|
This problem is not solved. I have had several Graphene updates since then. Is there another place to look for crash information? |
ByteHamster
removed
Needs: Reply
|
Here Graphene users have the same problem with other apps: https://discuss.grapheneos.org/d/9676-vanadium-tried-to-use-native-code-debugging Your best chance is to settle this with the Graphene community, as it is not AntennaPod specific and we can't support system components misbehaving |
|
@ByteHamster it appears these people are interested in why they are getting the notification, but in the case of AntennaPod it results in a crash, and this occurs when I allow native code debugging. Essentially, I don't know how I can know that this is a system component, as it may simply be a symptom of an AntennaPod crash. For example, if the timeline is like this:
In this situation (which is my suspicion is the real situation) the native debugging notification is not causing the crash. |
|
@ByteHamster Vanadium trying to use ptrace after the app using the WebView crashes definitely isn't the cause of the crash. We do probably need to figure out how to disable that but it's not the source of the problem. |
|
Based on the crash log in the initial report, this is triggered due to the quick tile doing something that it's not allowed to do. It has no connection to Vanadium beyond the annoyance we're aware of where it will try to use ptrace when not allowed to use it after an app crashes. |
|
The stack trace in the initial report is unrelated. Its time stamp does not get updated on further crashes, as @benmordecai confirmed above. (that other crash is reported and fixed in another issue) Given that this started without any AntennaPod update (but probably with a Graphene update), I'm still convinced that this is not caused by AntennaPod. In the past, we had faulty WebView updates occasionally which had a similar effect: Android kills processes that used the crashed WebView. @benmordecai An |
|
I'll try to attempt adb logcat after a crash. |
|
Here is a logcat about 10s after a crash |
|
Unfortunately that log contains just 2 seconds of data, and AntennaPod is not running (nor crashing) in those 2 seconds. Does Graphene not keep a log buffer? Maybe the log buffer is disabled in the developer options? |
|
If system logs are needed, after reproducing the crash, one can also go to Settings > System > View logs and save them to a .txt file from there. |
|
I have no idea. There was just so much text I terminated it. I can try to run logcat before a crash and wait for a crash to happen. |
|
System log immediately after crash |
|
Yup, that's a crash in Vanadium, not in AntennaPod... Your best chance is to settle this with the Graphene community, as it is not AntennaPod specific and we can't support system components misbehaving |
ByteHamster
added
Needs: Upstream fix
|
Thank you for looking into this. |
|
This appears to be an upstream Android / Chromium bug due to https://issues.chromium.org/issues/40824327 not being properly resolved between Chromium and Android. It's an issue on Android 14 QPR2 and Android 15 DP1 in general, not specifically GrapheneOS or Vanadium. You can see them talking about it there. Vanadium's renderer is killed for making a disallowed system call and this would likely also happen with Chrome on the stock OS. |
|
News from GrapheneOS colleagues:
|
|
More good news in GrapheneOS/Vanadium#480 (comment) |
Checklist
App version
3.2.0
Where did you get the app from
F-Droid
Android version
Graphene OS 2024-03-15
Device model
Pixel 6a
First occurred
a few days ago
Steps to reproduce
Expected behaviour
Normal operation
Current behaviour
Playback stops Graphene OS reports "Vandium Web View Tried to Access Native Code Debugging"
Logs
Environment
Android version: 14
OS version: 5.10.209-android13-4-g5944b4cc23fb
AntennaPod version: 3.2.0
Model: Pixel 6a
Device: bluejay
Product: bluejay
Crash info
Time: 02-01-2024 17:11:30
AntennaPod version: 3.2.0
StackTrace
The text was updated successfully, but these errors were encountered: