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

Repeating crashes while refreshing feeds #4467

Closed
2 tasks done
mmirg opened this issue Sep 29, 2020 · 2 comments
Closed
2 tasks done

Repeating crashes while refreshing feeds #4467

mmirg opened this issue Sep 29, 2020 · 2 comments

Comments

@mmirg
Copy link

mmirg commented Sep 29, 2020

Checklist

  • I have used the search function to see if someone else has already submitted the same bug report.
  • I will describe the problem with as much detail as possible.
  • [ x If the bug only to occurs with a certain podcast, I will include the URL of that podcast.

System info

App version: 2.0.0(6b173d0) Google Play

Android version: 11.0

Device model: Pixel 3 XL

Bug description

Steps to reproduce:

  1. Open AntennaPod
  2. Wait until feed refresh fails and application shuts down

Expected behaviour:

Refresh feeds or fail elegantly without interrupting UI thread and audio playback while providing detailed information about what errors caused the refresh to fail.

Current behaviour:

The feeds begin to refresh until everything stops and crashes. The same thing happens again after re-opening the software. This continues repeatedly until the refresh fortuitously completes successfully. Reducing concurrent downloads to 1 appears to help but does not solve the issue.

First occurred: (e.g. about x days/weeks ago)
Last year, around the time that the new version 2 betas began to roll out with a new UI.

Environment: (Settings you have changed (e.g. Auto Download). "Unusual" devices you use (e.g. Bluetooth headphones). Did you select another media player?)
Nothing unusual has been changed except for attempting to modify the number of parallel downloads.

Stacktrace/Logcat:

Crash info

Time: 29-09-2020 18:36:27
AntennaPod version: 2.0.0

StackTrace

java.util.concurrent.TimeoutException: com.android.internal.os.BinderInternal$GcWatcher.finalize() timed out after 10 seconds
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:442)
	at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:190)
	at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:211)
	at java.lang.Daemons$FinalizerDaemon.runInternal(Daemons.java:273)
	at java.lang.Daemons$Daemon.run(Daemons.java:139)
	at java.lang.Thread.run(Thread.java:923)

Environment

Android version: 11
OS version: 4.9.223-g5bded8e40b62-ab6647920
AntennaPod version: 2.0.0
Model: Pixel 3 XL
Device: crosshatch
Product: crosshatch

Crash info

Time: 29-09-2020 18:49:53
AntennaPod version: 2.0.0

StackTrace

java.lang.OutOfMemoryError: Failed to allocate a 56 byte allocation with 0 free bytes and 0B until OOM, target footprint 201326592, growth limit 201326592
	at okio.Okio$4.timedOut(Unknown Source:0)
	at okio.AsyncTimeout$Watchdog.run(SourceFile:327)

This issue appears to be in there same genre as #4446 and #2312 but the severity of my issue appears to be more extreme (insofar as it materially affects my ability to use the software at all) and some of my stacktraces appear different. It is very difficult for me to capture a stacktrace due to the repeated crashes. As you can see above, I have two produced within ten minutes of each other and there were several crashes in between. I was not able to use the software at all during that time period.

@ByteHamster
Copy link
Member

Could you please send me a database export, so I can see if I can reproduce this on my device? You can either post it publicly (be careful, listening behavior or passwords might be exposed) or just send me an email to info@<my username>.com.

@ByteHamster
Copy link
Member

Thanks, I received your export. Unfortunately, I can not reproduce the problem. Refreshing works fine after importing the database. As this seems to be the same as #2312, I will close your issue to keep everything in a single location. (having different stacktraces is normal for this kind of crash)

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