EDGE Crashing

[mradrianmarsh]

Which version of floccus are you using?

v5.8.3

How many bookmarks do you have, roughly?

thousands

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Google Drive

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Edge 143.0.3650.139

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

Whilst trying to sync, Edge crashes out. Nothing shows in the event log.
If I disable Floccus as an extension Edge doesn't crash.

Then I disabled Time and Change automatic sync.. And again Edge stays running.
Then I switch to uni-direction sync (to download from the cloud), and force a sync - then Edge crashes.

This has happened a few times now, and I usually find that deleting the local bookmarks file in Edge, then forcing a resync fixes it. But then a few months later it happens again. This time around, closing Edge, deleting the bookmarks file, hasn't helped.

Expected Behavior

Floccus shouldn't crash the browser

To Reproduce

Simplest method: I just start Edge... and then floccus crashes out taking the entire browser with it.

floccus-5.8.3-2026-01-16-redacted.log

Debug log provided

• I have provided a debug log file

[github-actions]

Hello! 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! 💙

[mradrianmarsh]

Just to add: I can see the logs are zero size. I've tried both redacted and full - both are empty after I restart the browser post-crash

[mradrianmarsh]

Double checked; Sync to cloud within Edge is disabled

[mradrianmarsh]

In my Chrome browser - if I merge-sync there, no problems it syncs without any crash or error

I've been able to delete the Bookmarks file in Edge and have edge start up with "no favourites" and then tried to force a download again - still crashes.

[mradrianmarsh]

Post clear-bookmarks + download + crash...

I can see floccus was able to populate favourites. I wonder if there's something in the bookmarks.xbel file that the edge version of the plugin isn't liking.

[mradrianmarsh]

So I've also tried:

• Clearing bookmarks file locally, restart edge - import from Chrome one-time - this worked, but as soon as I tried floccus again, Edge crashed out
• Forced an upload from Chrome to google drive - no problem. Tried to force a download in Edge - crashes out.
• Uninstalling flocuss - then reinstalling, setup again, setup as no-time,no-change,download only. Forced a download, and it crashed out again

I'm out of ideas at this point past a reboot-just-to-try..

[mradrianmarsh]

Nope... reboot made no difference either :-(

[marcelklehr]

Hello @mradrianmarsh
Thank you for taking the time to give feedback by opening this issue.

How many bookmarks do you have, roughly?
thousands

This is likely the cause: The browser may crash due to memory constraints that are hit by the large amount of bookmarks in floccus. I've been working on reducing the memory footprint for large amounts of bookmarks in recent weeks and will publish these improvements in the upcoming release soon.

[mradrianmarsh]

Hi @marcelklehr

Nothings changed in terms of the numbers of bookmarks for months, years. Anything I can do with the logging to try and capture if that's the case ? All the log files keep coming out blank. I did a quick check with Edges de-duplicator but none showing. I couldn't find anywhere to "count" the number.

I have a plugin MarkMagic for testing bookmark validity, it says 2351

[marcelklehr]

2351

That's not as much, indeed, I assumed you had more. I will try to reproduce this.

[mradrianmarsh]

@marcelklehr let me know if I can give any more info to you here.