Skip to content

App crashes when during start #896

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

Closed
gerroon opened this issue Jan 5, 2020 · 3 comments
Closed

App crashes when during start #896

gerroon opened this issue Jan 5, 2020 · 3 comments
Labels

Comments

@gerroon
Copy link

gerroon commented Jan 5, 2020

Hi

I am moving the bug entry from #890 to here.

Environment details

wallabag app version:
2.3.0

wallabag app installation source (e.g. Gplay, F-Droid, manual):
Fdroid

Android OS version:
LineageOS 14.1

Android ROM (e.g. stock, LineageOS, SlimRom,…):
LineageOS 14.1

Android hardware:
Samsung

wallabag server version:
Version: 2.3.8

Do you have Two-Factor-Authentication enabled?: yes/no
No

The app keeps crashing afterward a full sync, even when it is a fresh new setup. I was able to load all the articles and browse couple articles. Then I restart the app now it constantly crashes.

I tracked this issue down to huge articles I added recently. Deleting those articles from the server makes the app stable again. Please see the link below for the article list, I do not know which one causing it, but by removing those from my instance I was able to make the app work properly again. beware, some of those articles are very large.

App logs

https://paste.debian.net/hidden/442fe10b/

Url list (use wallabagapp as the password)

https://bin.privacytools.io/?bf06ba86a3e2cd6d#xxek7y9/M5XBnhclOb1qANzznvUHMRBLR4N6L31JOQY=

@di72nn
Copy link
Member

di72nn commented Jan 5, 2020

For searchability: java.lang.IllegalStateException: Couldn't read row 0, col 0 from CursorWindow.

Yeah, this looks exactly like #413, except this time there's a bit more logs available.

Unfortunately, I don't think there's much can be done until recent changes get released.

Were these large articles near each other in the lists? There's a chance that it won't crash if they are dispersed a little.

@gerroon
Copy link
Author

gerroon commented Jan 5, 2020

Yeah they were added sequentially.

@di72nn
Copy link
Member

di72nn commented Apr 4, 2020

Mostly likely fixed with #874.

@di72nn di72nn closed this as completed Apr 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants