Extension deactivate method on browser reload scenario.

[AxelFlores1990]

Hi! how are you?

I find some issue when the deactivate method of extension was executed on browser tab reload..

The deactivate was executed, but in standalone version, vscode provide 5 secs of grace period(as metion here) to stop every process before shutdown the host process..

I think that in web browser this 5 seconds was not provided as grace period..

We use the activate/deactivate methods to run a daemon process that works as a runtime to provide some services.. and in the standalone version it stop fine, but in the web browser the stop process was interrupted drastically...

Do you know if this is an issue or if theres any other way to map the reload tab event from the extension side?

[jsjoeio]

This is an interesting question! Do you know if this happens in Codespaces? If so, it's worth mentioning upstream. If not, then it's in code-server and we should probably fix it.

Maybe @code-asher has some insight.

[AxelFlores1990]

I need something more concrete to open the issue from vscode side.. you say seems likely.. I understand that vscode doesen't have any web logic, so why it gonna be responsible of something related to browser operation?

[jsjoeio]

Did you try reproducing it in Codespaces? I think that'd be enough to open an issue

[AxelFlores1990]

To be honest with you i never use code spaces... you could't debug the process to check if its problem of vscode event propagation or if its not correctly handled by code server?

[jsjoeio]

Oh it's pretty straightforward to use: https://github.com/features/codespaces

No, but if you provide clear steps to reproduce and an extension to try it with, happy to try locally.

[AxelFlores1990]

Okas, Im going to try with codespaces to provide the error scenario