Question about "high energy (power) usage".

[gaveitatry2]

The energy (power) usage should be higher than VM as well, but this needs time to make coding improvement.

In terms of energy usage, VM and FM are the best I believe.

@cyfung1031 - What did you mean by high energy power usage? Does the ScriptCat extension cause Google Chrome to use more Memory? It seems that after I made the switch to ScriptCat from Violetmonkey, my Google Chrome uses 3500-4500 MB memory instead of the previous 2500 MB. But maybe I am mistaken. Maybe I just have more open tabs or something. Or did you mean CPU? I don't notice any difference in CPU usage at all.

@cyfung1031 - On a side note, I have another question. When will the beta be updated to the main branch? Like an estimate of how many weeks and months? I prefer using the main branch installed from the Chrome Web Store.

[cyfung1031]

I believe VM was doing much simple way for the userscript running.
In ScriptCat, the script codes and everything are stored in the memory. (in background service worker)
This can be checked in Task Manager (right click tab strip blank area)

It is storing the string data so not 1000 MB, but 40 ~ 400 MB

For CPU usage, if you have many scripts running, even they are inactive, there are many messaging mechanism so CPU usage should be higher than VM

I referred "high energy (power) usage" to this messaging mechanism which is not yet avoidable. Hopefully someday this can be improved.

If you have just few userscripts then it should be not noticable.
But I have 2xx+ scripts and 7x+ active scripts so I do feel this energy consumption issue.

On a side note, I have another question. When will the beta be updated to the main branch? Like an estimate of how many weeks and months? I prefer using the main branch installed from the Chrome Web Store.

The stable 1.2.0 is released and publishing in Chrome Store.
The beta version is not yet.
You can see all releasing here - https://github.com/scriptscat/scriptcat/releases
There is no fixed scheduling - depends on the severity and necessity.
In VM, they just do the stable/beta in a very messy way. stable is not stable. beta is not beta.
But in ScriptCat, stable really means well-tested. beta is for the new features.

ScriptCat 1.2.0 stable is usable and which will be the latest version in market.

[gaveitatry2]

Why does ScriptCat 1.2.0 seem to be using less memory than ScriptCat 1.1.2? Is it my imagination? It has to be. Because you said script codes are stored in the memory, and probably nothing has changed since v1.1.2.

[cyfung1031]

I think your excessive memory usage is not due to the stored script code.
There are many many coding changes from 1.1.2 to 1.2.0 (including both core scripting and UI design). So some memory leakage bugs might have been fixed as well.

[cyfung1031]

https://chromewebstore.google.com/detail/scriptcat/ndcooeababalnlpkfedmmbbbgkljhpjf

ScriptCat 1.2.0 Stable is published in Chrome Store

[gaveitatry2]

@cyfung1031

Yay!

Thank you for letting me know.

The orange badge means that there is no enabled scripts on the page, right? It scared me. I thought that something broke or that there was an important notice that I could not find. Honestly, I think that no badge or just a blank blue badge would be better than a bright, contrasting orange with an exclamation mark in it. Should I make an Issue (feature request) for that?

Thank you for the update to the extension. I don't know what changes were made, but I am sure that I will they were good changes.

[gaveitatry2]

When you click it, it should you the warning, telling you the Userscripts API permission is not yet granted.

My userscripts are working on every website that has active running userscripts. The orange badge only appears on websites that don't have active running userscripts. There is no warning message anywhere. If I click notifications, there is just a blue information icon but no warning message.

chrome_Vum40DzbDa.mp4

[CodFrm]

You need to reload the extension (close and reopen it), or restart your browser:

https://docs.scriptcat.org/en/docs/use/open-dev/

[gaveitatry2]

You need to reload the extension (close and reopen it), or restart your browser:

https://docs.scriptcat.org/en/docs/use/open-dev/

I did restart my browser. That was one of the first things that I tried. But I haven't tried disabling and re-enabling it. I will try that now.

[gaveitatry2]

You need to reload the extension (close and reopen it), or restart your browser:

https://docs.scriptcat.org/en/docs/use/open-dev/

Restarting my browser did not work. But disabling and re-enabling the ScriptCat extension did work. Thank you.

[CodFrm]

This might be related to the background feature being enabled in version 1.2.0; your browser may not have actually closed completely. This issue was resolved in the next patch.