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

No more current or recent sessions after moving to a new computer #227

Open
pierswalter opened this issue Jan 16, 2024 · 1 comment
Open
Assignees

Comments

@pierswalter
Copy link

I've been using extension version v7.1.6.2 for years now.

This week, I've moved to a new computer, and the extension does no longer fully work.
While previously stored sessions are still available, no current or recent sessions are being displayed.
So new windows and tabs are no longer stored.

Has anyone else experienced such a problem?

Could this have something to do with the change of OS (from macOS 13 Ventura to macOS 14 Sonoma) or with the change of processor architecture (from Intel to ARM)?
Both sound unlikely, but I mention them just to be sure.

There may also have been a Chrome update in between, I'm currently using Chrome 120.0.6099.234.

@pierswalter
Copy link
Author

I'm pleased to be able to report that one day and several reboots later, the Marvellous Suspender works again.
The current and recent sessions are once again being displayed.

I do not know what brought about this change, but I would like to share one observation before closing this issue.

Yesterday, when it did not work, I tried to inspect the stored sessions using the Chrome devtools.
In the devtools, I went to the Application tab, expanded Storage > IndexedDB, and looked at the contents of tgs > gsCurrentSessions.
No content was displayed in the main view on the right side.
However, the status bar below the main view displayed: Total entries: 6

Today, the status bar once again displays: Total entries: 6
And now the main view also displays these six recent sessions.

This leads me to suspect that this might have been more of a Chrome issue than an issue with the Marvellous Suspender.

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

No branches or pull requests

2 participants