-
Notifications
You must be signed in to change notification settings - Fork 921
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
[Bug] Crashing with large bookmark list #4951
Comments
Thank you for opening an Issue in our Repository. |
This comment was marked as resolved.
This comment was marked as resolved.
Ah. I think the fix you cited is for Windows, not Android |
@JackDSRS I see you’re on 5.198.0, is it possible to update the app and see if it resolves the issue? (Latest F-Droid release is 5.209.2). |
It worked great! So great, I decided on a torture test. I openened 10 tabs, then restarted my tablet. On restart, I put memory under load opening 5 apps, one of them a video player in an opened running pop up state. I opened DuckDuck with the 10 tabs open, and flipped down to the bottom of the bookmark list, back to the top, then into several folders. No crashes. Thank you so much for the follow up! |
@JackDSRS Glad it’s working as expected now, I’ll let the team know. |
Describe the bug
This ONLY happens after I restart my tablet, not my phone, and start the browser for the first or second time. It does not happen any time opening it after that. It happens even with no other tabs open.
I have many bookmarks. I'll guestimate 100, most organized by topic. 19 are Favorites. It happens regardless if favicons are on or off. And yes, I use most. I do research, share to other apps, or other people. I also have shortcuts on my home screen. Starting after boot from shortcut apps for the first or second time after boot, instead of the browser itself also results in crashing.
I regularly clean optimize my devices, but DuckDuck is whitelisted for everything an installed on Internal storage. No battery optimization, never sleeping, never disabled, frozen, or 3rd party memory oprimized during operation, bootup, or wake-lock.
It's the default browser, and the latest F-Droid release. I use the non-paid services, with the app tracker blocker, email protection, and cookie popup enabled. App tracking blocker starts on boot with no issues.
I have a Samsung Tab A. The phone with no problems but far less bookmarks is a Samsung Note 10+. Both are running Android 10. Neither are rooted and are using the original stock roms.
This issue began about a year and a half ago maybe. Its survivable, but continues, so I thought I'd finally report it.
Every test I've tried has tied this to the bookmarks. Real-time memory monitoring hasn't indicated an overly sharp drop in memory in opening the browser prior to crashing.
How to Reproduce
As listed above
Expected behavior
Not crashing
Environment
The text was updated successfully, but these errors were encountered: