Errors caused by _suspensionQueue being undefined

[LeXofLeviafan]

If I attempt using the extension after a period of inactivity, the service worker would sometimes get stuck in the Inactive state (ignoring user actions and displaying a suspended pages as blank). Checking it in Extensions view shows two TypeErrors within js/gsTabSuspendManager.js (lines 60/unqueueTabForSuspension() & 204/getQueuedTabDetails()): "Cannot read properties of undefined" (both pointing at methods of _suspensionQueue).

It appears that _suspensionQueue might not be re-initialized correctly when restoring service worker that was unloaded from memory 🤔

[LeXofLeviafan]

…Alternatively, service worker being unresponsive might be actually related to this Chrome bug instead 🤔

(Doesn't mean that _suspensionQueue errors should not be fixed though 😅)

[rkodey]

So far I have not found any way to produce this error. All 3 tab processing queues in the extension are designed to automatically re-initialize themselves when the service worker stops and restarts. So, the real problem here is whatever is causing the "stalled" service worker that results in the blank suspended pages. This might be a tricky one to pinpoint.

@LeXofLeviafan - Can you let us know how you've configured TMS? Specifically, what are your settings:

• Automatically suspend tabs after
• Apply Chrome's built-in memory-saving when suspending ( on or off )

Thanks!

[LeXofLeviafan]

• "Automatically suspend tabs after" is set to "Never"
• "Apply Chrome's built-in memory-saving when suspending" is on

I also use it both in main Chrome window and in Incognito windows, but they seem to be using separate worker instances, which operate independently (e.g. when the main window worker "freezes", the Incognito worker still operates as before) 🤔