sessions disappeared after crash

[Marcelo Magno]

Hi,

after a crash my sessions have disappeared. Tryed to follow restore tips on sessionbuddy.com, but importing files did not manage it.

I can see theese folders:

chrome-extension_edacconmaakjimmfgnblocblbcdcpbko_0.indexeddb.leveldb

chrome-extension_edacconmaakjimmfgnblocblbcdcpbko_0.indexeddb.blob

I can see a file named chrome-extension_edacconmaakjimmfgnblocblbcdcpbko_0.indexeddb.blob/3/03/3c7 of date 2024-09-04 14:34:13 (the time of the system crash), and opening in a text file I can seed more or less the sessions that I was using at that time.

trying to use restore option or import options on this file did not made it (gives error: invalid session buddy export file).

Also tryed this link (https://sessionbuddy.com/v4-migration/) to try to open that file but gives error "Invalid Session Buddy v3 database file"

Can you please adivise-me how can I restore my lost sessions?

 

[Session Buddy Support]

Are there any errors in the console when SB loads?

https://sessionbuddy.com/console/

Can you send diagnostics? (go to Settings > Other, then click "Save diagnostics").

Are you able to Export? Click the gear menu, then Export.

If Export is successful, great. Keep this file.

If not, try running this command in the console:

saveData()

Does the export or saved data file contain your collections and history?

Hans

--
You received this message because you are subscribed to the Google Groups "Session Buddy Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sessionbuddy-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sessionbuddy-discuss/db341baa-c164-497d-915e-ca626342f33en%40googlegroups.com.

[Session Buddy Support]

Meant to mention you can send diagnostics directly to sup...@sessionbuddy.com 

Hans

[Marcelo Magno]

Hi,

in console there are errors:

----- service worker load 9/4/2024, 4:39:48 PM -----
background.bundle.js:2 Uncaught (in promise) r
main.bundle.js:2 ----- app load 9/4/2024, 4:41:00 PM -----
main.bundle.js:2 local storage usage: 20.34%
main.bundle.js:2 failed to fetch history: Failed to read large IndexedDB value
 DataError: Failed to read large IndexedDB value
fetchNavClientHistoryFailed @ main.bundle.js:2----- service worker load 9/4/2024, 4:39:48 PM -----

background.bundle.js:2 Uncaught (in promise) r
main.bundle.js:2 ----- app load 9/4/2024, 4:41:00 PM -----
main.bundle.js:2 local storage usage: 20.34%
main.bundle.js:2 failed to fetch history: Failed to read large IndexedDB value
 DataError: Failed to read large IndexedDB value
fetchNavClientHistoryFailed @ main.bundle.js:2

diagnostic file attached: 

exporting collection gives me error to, log file generated in console in attached log file:

typing saveData() in console generates a json file that appears to be only the blank session with the new created sessions after crash, not the previous sessions before the crash.

Thanks in advance for yout kind help.

regards,
Marcelo Magno

You received this message because you are subscribed to a topic in the Google Groups "Session Buddy Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sessionbuddy-discuss/QooXDKRbjvw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sessionbuddy-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sessionbuddy-discuss/CAAqiLL-AO04sSw3dSdv1toe3pmy%2BPoxBgapDj__hOxz50Hqtow%40mail.gmail.com.

[Session Buddy Support]

Thanks for the info.

Unfortunately it looks like you've encountered a Chrome bug.

More details here:

Large/complex IDB randomly fails with DOMException: Failed to read large IndexedDB value [342779913] - Chromium
https://issues.chromium.org/issues/342779913

We're working on a local backup feature as well as a cloud storage feature that will minimize (or eliminate, in the case of cloud storage) the impact of Chrome bugs such as this. In the meantime, the only way to recover data lost to such a bug is from a system backup or Session Buddy backup, if you have either.

Hans

To view this discussion on the web visit https://groups.google.com/d/msgid/sessionbuddy-discuss/CAPGAtGTWuotvp6hxOcRRz%2BhmMsG0fUAZKyjfxmc6m8VrJRsPKA%40mail.gmail.com.

[Marcelo Magno]

Thanks for the link. I have read, but did not recognize if there is a way to recreate the broken db or what to do.

As I told you before, there are files in the Default/IndexedDB/chrome-extension_edacconmaakjimmfgnblocblbcdcpbko_0.indexeddb.blob/3/03/ directory that upon reading it in a text editor, I can see some my old sessions.

Isn't there a way, using one of these old files (there are a lot of them) to reconstruct even part of the missed sessions? 

I also tried to delete the files that were created after the crash (deleted today and yesterday files that were created in these files - I have a backup from yesterday) but after deleting these files, I can't see the old data in history and I continue to see the "Failed to read large IndexedDB value" in the console. I don't know how this chrome indexed db works, but isn't there a way to have the old files, to try to get some of the information or a way to try to recuperate the broken db using the old files that are there? I was thinking that by deleting the files generated after the crash (with chrome closed) upon starting the chrome again, I could detect and repair the db and go back in time for the time before the crash. I think that there's more to do to achieve this but I don't know how the indexeddb works.

Can you please advise?

regards,
Marcelo Magno

To view this discussion on the web visit https://groups.google.com/d/msgid/sessionbuddy-discuss/CAAqiLL-HMnuBGXMcT4m5bRDzcivj7-Eaw%3DF4%3D1O9fZ%3DRy6AHsw%40mail.gmail.com.