Google Maps (and some others) fails with too many gsScrollPos

[alberthdev]

This seems to happen with a long-running Chrome, with many Google related tabs open. When opening Google Maps, the map images themselves refuse to load. The Developer Console indicates that Google is returning a HTTP invalid request error, due to too many gsScrollPos cookies stored for their domain. Removing a good chunk of those cookies resolves this issue.

Using the latest The Great Suspender v6.30 (webstore).

[deanoemcke]

This is essentially a duplicate of this issue: #537

There will be a new release on the webstore soon to address this issue. Sorry for the inconvenience.

[jellonek]

Can you give an approximation of time when this issue will be addressed?

[higstar]

Is there a workaround for this? i.e. set maps to no suspend?

[deanoemcke]

@higstar I imagine that if you cleared your cookies and then whitelisted maps, you would not encounter this problem anymore.

@jellonek My current optimistic timeline is April. Fingers crossed.

[alystair]

Any update? I just googled for "gsScrollPos" and found this, go figure it was caused by this extension...

[deanoemcke]

Keep an eye on #537 for updates.
I'm pushing really hard for the release right now.

[Ratismal]

So, this issue has been open for almost a year. I know that for me, personally, it's really annoying to deal with - every so often, I have to open content inspector and delete all of the hundreds of cookies TGS created. Which is a shame, since otherwise the extension is really good.

The good news is, while I don't have a fix, I have a solution! I created a simple userscript (for tampermonkey, greasemonkey, etc) which deletes all cookies named gsScrollPos-X when you open any page.

I hope that it provides some much-needed relief for you all.

Link: https://github.com/Ratismal/tgs_cookie_killer

[rannmann]

It's not ideal, but I run this whenever the maps stop loading:

function clearGSScrollCookies() {
    var cookies = document.cookie.split(';');
    for(var i = 0; i < cookies.length; i++) {
        var cookieName = cookies[i].trim();
        if (cookieName.match(/^gsScrollPos\-/)) { 
            console.log("Deleting " + cookieName);
            document.cookie = cookieName + '=; Max-Age=-99999999;';
        }
    }
}

clearGSScrollCookies();

[luixal]

Hey @rannmann , that works like a charm! Thanks!

[frederickjh]

It's not ideal, but I run this whenever the maps stop loading: . . .

@rannmann Where do you add run that code?

[DaveKap]

This is still a problem and I still hate it.

[frederickjh]

Thanks @Ratismal for the user script!

[Jollfye]

@luixal, @frederickjh, @DaveKap hm if u still have this gsScrollPos issue I think u r using now old 6.30 TGS extension version, a lot was fixed since then, including this bug, I suggest u to update to latest Chrome Web Store 7.1.0 version as I wrote bout it here.

[DaveKap]

@luixal, @frederickjh, @DaveKap hm if u still have this gsScrollPos issue I think u r using now old 6.30 TGS extension version, a lot was fixed since then, including this bug, I suggest u to update to latest Chrome Web Store 7.1.0 version as I wrote bout it here.

Thank you for this! I had no idea my version was out of date. Why the hell isn't the extension auto-updating?

[frederickjh]

@Jollfye the extension would not upgrade to the new version without first uninstalling the old version in my case. Waiting to see if this fixes it as I could go days or weeks before the gsScrollPos issue would rear its ugly head.

[Jollfye]

@DaveKap, @frederickjh, yep that not auto-updating thing, only manually or through uninstall, I met it too (long ago) but I guess actual developer @deanoemcke may have a clue why.. and yes, I think the bug should be gone the moment u run latest TGS extension version coz now scroll position is being stored in suspended tab's url, not in cookies as before, so gsScrollPos should also be gone and u should never see it again 😅

[Avamander]

For some reason I hadn't still gotten the new version from Chrome web store. Had to manually uninstall and reinstall.

[frederickjh]

I haven't see this issue rear its ugly head since my last post about updating in April. I consider it fixed.

[Avamander]

It's not fixed if people are not getting the update.

[frederickjh]

@Avamander That is another related issue that the update will not install without first uninstalling The Great Suspender chrome extension.

If that is something that cannot be fixed, so that the extension can auto update, at the very least the information that you need to uninstall to upgrade to the newest version should be added to the extension's page on the chrome web store.

Do we know what version will not update automatically but needs to be uninstalled first? I see that the OP of this issue was on version 6.30. I am currently on version v7.1.0, but do not remember what version I was on before I uninstalled.

If we can figure out the version that I can create an issue to have that information added to the great suspender chrome web store page.