Opened editor won't be closed, consuming CPU usage.
taxen opened this issue · 1 comments
I have just started to use the extension for Chrome on Windows 10 64 Bit.
Precisely, Windows version is Windows 10 Home 22H2. OS build is 19045.2846.
Chrome is 113.0.5672.127（Official Build）, the latest at the moment.
I am trying to use the extension to open a file (on my local PC with a text editor) which is directed by a selected text on a web page.
The text editor is called Hidemaru. Direct link to download is here. Introduction page (only in Japanese) is here.
After setting up by following your video, the extension successfully launched the file in the editor.
The problem was... the tab opened by the extension would not seem to work. It would not be closed. Rather, the tab would not accept any input except tab selection by mouse. So, I could not edit anything on the tab, not even one letter.
Other tabs already opened had no problem in closing while the tab in trouble also opened.
When I looked at task monitor, the tab process uses 20%+ CPU power all the time.
There are two processes launched before the editor process. They are by cmd.exe and node.exe
For cmd.exe, the command line is
C:\WINDOWS\system32\cmd.exe /d /c "C:\Users\user\AppData\Local\com.add0n.node\run.bat" chrome-extension://bifmfjgpgndemajpeeoiopbeilbaifdo/ --parent-window=0 < \.\pipe\chrome.nativeMessaging.in.6c3c83360b70c394 > \.\pipe\chrome.nativeMessaging.out.6c3c83360b70c394
For node.exe, that is
"C:\Users\user\AppData\Local\com.add0n.node\node.exe" "C:\Users\user\AppData\Local\com.add0n.node\host.js"
When I forcefully closed the two processes, the tab process was also terminated. At the same time, already closed session of the editor resumed, seemingly the resumed process was suppressed until then.
I do not know which one to be blamed, either the extension or the editor.
Actually, this issue had been bugging me for firefox as well. Ever since the extension moved from the good old style to web extensions , the issue persists. The fact that the new extension would not work for the text editor is the only reason I have kept using old firefox until quite recently.
Can the developer look into the issue? I will also contact the developer of the text editor.
Sorry to bother you.
After updating the text editor to the latest version, the issue was resolved.
I wish [SELECTIONTEXT] argument also works for toolbar button.