Enabling the plugin causes Google Chrome to crash. #1947
Comments
|
Hello 👋 Thank you for taking the time to open this issue with floccus. I know it's frustrating when software 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, Thank you for reading through this primer. I look forward to working with you on this issue! |
|
Hello @wxyShine |
|
I have exactly the same issue on both Chrome and Edge and on multiple PCs |
|
The firefox issue turned out to be a non-issue. I can currently not reproduce this with 136.0.7103.92 on linux. Are you on Windows, Mac or Linux/Unix? |
|
Confirming I also have this issue. Seems to be affecting Chromium based browsers. I have Brave, Edge, and Chrome on multiple windows pc. Browsers start up fine until Floccus starts syncing and immediately crashes them. |
|
Also experiencing it here. Running on Windows, I have multiple Edge and LibreWolf browser profiles and the problem only occurs in Edge profiles. I am not yet certain but currently I think that it happens only when I have made a change in bookmarks in Edge browser profiles. Conversely, making a change in a LibreWolf browser profile and syncing to Edge does not seem to cause the problem. Once it starts happening in any Edge browser profile, it continues happening as soon as Floccus begins to try and sync. To cure the problem (at least until it begins again), I have to uninstall Floccus from Edge, reinstall it, recreate the Floccus profile, and then I can do an initial sync successfully. Edge 136.0.3240.64 on Windows 11 Pro 22H2 (yes, I know, old). Additional:- |
|
I might have useful information (EDIT: maybe not, see bottom) as to why this is happening. I have only had floccus for three weeks or so, but in the last week this has been happening to me as well. This seems to happen, at least for me, during the quirk that exists wherein if you close the browser during a sync, the extension exercises caution such that reopening the browser results in a "sync scheduled" notification that leads to no sync for two hours, for whatever mysterious reason (all this is in the FAQ on the floccus site). Every time this happens to me, that is what floccus is saying on that browser in the two seconds I have before Chrome closes--that the sync is scheduled, pending things getting sorted out. The browser on the other device without the warning will stay open just fine. Reinstalling floccus fixes it until the sync is scheduled again (presumably because you closed the browser during a sync, but I can't swear to that), and then you are out of luck all over again. No way out except reinstalling (or, once it is reinstalled, opting for manual syncs only to avoid closing the browser mid-sync. Or you could just always make sure it is not caught mid-sync when you close your browser, assuming this bug is not resulting in a scheduled state for some other reason. Not great options, but hopefully will tide people over until the developer can make a fix). It is possible I am misinterpreting, and the scheduled state results from the initial crash, but the extension is capable of carrying on normally without crashing Chrome for days, so it does seem possibly related. EDIT: decided to close the browser during a sync to force the issue. Sync is now scheduled but the browser stays open. Would this be different if another element had been different ( I did have autosync turned off at the time for at least one of the devices, and it may have also previously been an issue of the browser getting closed from the other device first rather than on the same machine)? Maybe? But I don't have the time to experiment endlessly, so that's all from my end. |
|
I got a hold of a Windows machine, but have so far been unsucessful in reproducing this :/ Edge 136.0.3240.64 |
|
I think we are all syncing to Google Drive. Have you tested with that? |
|
Yes, Google Drive and WebDAV with a few thousand bookmarks on both Edge on Windows and Chrome on Windows. I have a hunch it may have to do with the new logging system, which may be accumulating too much data. Could you try downloading the debug logs in the profile settings of a profile of your choice. Would be interesting to see how large that file is. |
|
I have almost 11,000 bookmarks, so it may be you need to test with more than you are.
I tried to download the logs but pressing that button crashes Chrome, so it’s not possible to do so. (Tried multiple times). Is there a location on a Windows machine where I can pick them up directly?
Many thanks.
Michael
|
|
Tried with 18k Bookmarks, via both GDrive and WebDAV. This produced 100MB of logs for me but nothing crashed. Is there a way to find out more about these crashes from your end? Any details you can gather from a crash report or something? |
|
Chrome Debug Log just generated and available here:
https://www.dropbox.com/scl/fi/m1i0bnys1sc523r3wxaxh/chrome_debug.log?rlkey=y5fvf8vpebp2cotlavqby2415&st=6jko1ory&dl=0
Chrome crashed immediately I reenabled floccus.
|
|
Can you confirm that using an older version of chrome does not show this behavior? |
|
Yes. It only started happening following the latest update.
Michael
Sent from my iPhone
…________________________________
From: Marcel Klehr ***@***.***>
Sent: Saturday, May 10, 2025 6:20:55 PM
To: floccusaddon/floccus ***@***.***>
Cc: Michael Kraftman ***@***.***>; Comment ***@***.***>
Subject: Re: [floccusaddon/floccus] Enabling the plugin causes Google Chrome to crash. (Issue #1947)
[https://avatars.githubusercontent.com/u/986878?s=20&v=4]marcelklehr left a comment (floccusaddon/floccus#1947)<#1947 (comment)>
Can you confirm that using an older version of chrome does not show this behavior?
—
Reply to this email directly, view it on GitHub<#1947 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKJYWGMOJCPUHV33XXBWWQ325YYPPAVCNFSM6AAAAAB4TFM3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNRZGAZTQOJRHE>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
I am experiencing the same issue, but in my case, I am syncing with Nextcloud. The behavior is essentially identical: Microsoft Edge automatically closes a few seconds after opening. However, if I quickly disable the Floccus extension before the crash occurs, the browser functions normally and does not close. |
|
Same issue here: |
I believe this is a bug in Chromium's garbage collector, judging from similar issues on their issue tracker. Finger's crossed that the next update will resolve this.
The debug log was not much help unfortunately, it merely confirms that after floccus starts the logs soon end (crash). The last error log entry may or may not be related, but unintelligble to me |
|
It would be interesting if it also crashes with an earlier version of floccus from the v5.4 series. Could you try installing this and reproducing? https://github.com/floccusaddon/floccus/releases/tag/v5.4.5 |
|
Hi
I’ve successfully downloaded 5.4.5 but it is not clear to me how to install that into Chrome. Could you please explain how to do that?
Many thanks.
Michael
|
|
It's happening to me on Chrome 136.0.7103.93 (Official Build) (arm64) syncing with github. I have only about 2100 bookmarks. |
I have avoided the problem for some time by making only small changes (additions, deletions, edits) in LibreWolf before syncing over to Edge. However, my luck ran out and on the latest sync Edge began to crash again. I decided to try Floccus 5.4.5 and I was able to sync successfully. Specifically I did the following: Annoyingly, the hanging issue seems difficult to reproduce consistently although on previous occasions with 5.5.3 and Edge 136.0.3240.64), it seemed that the only way to avoid it once it had started was to remove and replace Floccus and remove all my bookmarks from within Edge and allow them to be repopulated by Floccus from the server. Update at 01:14 GMT on 20250514 |
Not sure if you've got it installed but this should help if not (assuming you are on Windows): Now it should work. |
|
I have been struggling with this as well. I run a couple of different versions of browsers. Chrome Development - Started to have an issue last week As of today - Chrome Canary is crashing too. It's weird - if I remove the plugin, then setup - it does the first sync no problem and seems to work fine. But then the next day it's crashing, or a couple hours later. Windows 11 |
|
I am experiencing this syncing to WebDAV, running under Linux 64-bit. Happens on multiple systems. Chrome 136.0.7103.59 |
|
I have exactly the same issue on Edge and on multiple PCs |
|
I confirm that this rollback has solved the problem for me.
Many thanks.
Michael
Michael Kraftman
UK: +44 7780 601026 | USA: +1 (786) 661 8866
E: ***@***.******@***.***>
***@***.*** linkedin.com/in/mkraftman/<https://www.linkedin.com/in/mkraftman/>
From: Marcel Klehr ***@***.***>
Sent: 14 May 2025 13:56
To: floccusaddon/floccus ***@***.***>
Cc: Michael Kraftman ***@***.***>; Comment ***@***.***>
Subject: Re: [floccusaddon/floccus] Enabling the plugin causes Google Chrome to crash. (Issue #1947)
[https://avatars.githubusercontent.com/u/986878?s=20&v=4]marcelklehr left a comment (floccusaddon/floccus#1947)<#1947 (comment)>
I've now activated a rollback of the v5.5.x series on chrome back to v5.4.5 which (which will appear as 5.5.3.1 in chrome://extensions ).
—
Reply to this email directly, view it on GitHub<#1947 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKJYWGIYQGYZ6RXG36UJNSL26LSJNAVCNFSM6AAAAAB4TFM3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZYHEYTKMBTGE>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
|
I can confirm this is now working for me as well on Chrome Dev and Chrome Canary. Installed the newest version (rollback). Thanks for your effort! |
|
The reason for this crash is due to this massive ( >1gb ) MANIFEST file located in the extension directory. |
I can verify this, I also have a >1GB MANIFEST file in "AppData\Local\Google\Chrome\User Data\Default\IndexedDB" But what should we do now? Can we safely delete that file and Chrome will rebuild it? I don´t know exactly what to do with this information. |
You can delete it, then id recommend exporting your profiles and make sure you install the non affected version which means you probably need to delete and reimport anyways, but deleting will at least stop it crashing so you can export if you didn't have a profile export already. |
|
Chrome - solved with rollback! Edge - what is the status? |
|
The rollback is still in review from Microsoft. :/ |
Owch i just reverted mine manually as don't mind doing the process as this issue was making the extension unusable for me and im quite good with tech stuff |
|
I was having this issue with Edge as well apparently. I had thought it was something more generic for the browser; reinstalled completely and it seemed to be resolved, I just tried again and I'm back to crashing unfortunately. Deleting the contents of the LevelDB folder seemed to slow the crashing enough that I could disable Floccus at least. I might just leave it disabled in Edge for the moment as I don't really use it often.
|
|
Since the crash doesn't happen on my devices, can you please test the following build of v5.5.3, which hopefully does not have the crash issue and report back here: floccus-build-v5.5.3.2-chrome.zip (And as comparison, this should have the crash issue: floccus-build-v5.5.3-chrome.zip) How to install alpha/beta versionsChrome (separate testing installation)
|
|
@balthanon Would you mind testing? |
Just for info i reverted to previous and for me has been fine so far |
Didn't see this till just now-- I'll test that later today. |
|
Tested the new release and from what I can see, it isn't causing the same crashes. I only set up one of my three profiles tonight though; I'll try and set up the other two (which are larger) tomorrow. |
|
Edge is back to my standard set up with my full bookmark sync; no issues so far. I'll keep it running for today and see if it ends up with any issues as logs build up. (Edit: After a full day, no crashes or other issues that I detected; so seems like it fixed it to me.) |
|
Thank you @balthanon |
|
@balthanon If you still have some time, could you verify that the faulty build I linked above does crash for you, so we can be sure that we would have seen a crash if there was a problem? :D |
|
@all-contributors Please add @balthanon as a contributor for ideas, feedback and bug hunting. |
|
I've put up a pull request to add @balthanon! 🎉 |
Forgot to do that-- just loading it hasn't actually crashed Edge. I'll leave it running for a bit to test again. |
|
Updating this-- I haven't had a ton of activity, but still no crashing at this point with the second build. |
Which version of floccus are you using?
5.5.3
How many bookmarks do you have, roughly?
5k
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.
136.0.7103.93（正式版本） （64 位）
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
5.5.3 was functioning normally before the update, but after upgrading, Google Chrome became unusable. The browser crashes a few seconds after opening. Disabling this plugin allows the browser to function properly.
Expected Behavior
Open Google Chrome, and it automatically closes after a few seconds.
To Reproduce
Open Google Chrome, and it automatically closes after a few seconds.
Debug log provided
The text was updated successfully, but these errors were encountered: