Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BETA 4.18 No script #1528

Closed
oplle opened this issue Jun 14, 2022 · 16 comments
Closed

BETA 4.18 No script #1528

oplle opened this issue Jun 14, 2022 · 16 comments

Comments

@oplle
Copy link

oplle commented Jun 14, 2022

Frequently appear,
The new label opened a webpage for the first time,
No script,
Refresh the page will have scripts

Tampermonkey BETA 4.18.6163
Chrome 77

https://imgur.com/CQhVj4M
https://imgur.com/cmIgSyL

@derjanb
Copy link
Member

derjanb commented Jun 14, 2022

Please try 4.18.6164. (crx)

Chrome/Edge users, please download the crx file linked above and drag and drop it to the extensions page chrome://extensions.

Thanks.

@oplle
Copy link
Author

oplle commented Jun 14, 2022

Please try 4.18.6164. (crx)

Chrome/Edge users, please download the crx file linked above and drag and drop it to the extensions page chrome://extensions.

Thanks.

The problem still exists, this is a probability problem
https://youtu.be/R-pesq8T6Oc

@derjanb
Copy link
Member

derjanb commented Jun 14, 2022

Understood. Thanks.

Are you using special settings like "Instant" injection mode?
Can you reproduce this at newer Chrome versions like 102?

@oplle
Copy link
Author

oplle commented Jun 14, 2022

Understood. Thanks.

Are you using special settings like "Instant" injection mode? Can you reproduce this at newer Chrome versions like 102?

This problem is brought about by the recent new version. Other extensions or scripts are still old, and I won’t find out the problem.

I insist on this version of the browser,
It is because there is an extension that is very suitable for me, I have used it for 3 years
But the new version cannot be supported.

@oplle
Copy link
Author

oplle commented Jun 14, 2022

Please try 4.18.6164. (crx)
Chrome/Edge users, please download the crx file linked above and drag and drop it to the extensions page chrome://extensions.
Thanks.

The problem still exists, this is a probability problem https://youtu.be/R-pesq8T6Oc

Is there a previous version CRX before 4.18.6163,
I tes it, If valid, I keep the old version

@JourneyOver
Copy link

I was having this exact same issue with version 4.18.6163 albiet on a way more up to date version of chrome (102 now running 103) unlike oplle, except for the fact that sometimes a refresh wouldn't even temporarily fix the issue. Updating to 4.18.6164 seems to have fixed the issue however, though I'll need to do more testing. (think oplle's issue now stems from them using a way out of date version of chrome browser)

@ayasechan
Copy link

chrome version 102.0.5005.115
tempermonkey beta version 4.18.6164

same problem occurred

@derjanb
Copy link
Member

derjanb commented Jun 15, 2022

I see a similar issue when 4.18.6163 or 4.18.6164 are installed over a 4.17.* version. Sometimes scripts run and sometimes not. A complete browser restart helps and make everything reliable again. Please note, that often Chrome processes stay running even tough Chrome seems to be closed. @Skeeve for example had to log out to close Chrome completely.

So can someone please confirm that the issue is present after a logout or even better a computer restart.
Thanks.

@ayasechan
Copy link

I see a similar issue when 4.18.6163 or 4.18.6164 are installed over a 4.17.* version. Sometimes scripts run and sometimes not. A complete browser restart helps and make everything reliable again. Please note, that often Chrome processes stay running even tough Chrome seems to be closed. @Skeeve for example had to log out to close Chrome completely.

So can someone please confirm that the issue is present after a logout or even better a computer restart. Thanks.

Logging out or restarting the computer doesn't fix the problem
The problem was solved after I removed the user-data-dir and reinstalled the extension

@derjanb
Copy link
Member

derjanb commented Jun 15, 2022

The problem was solved after I removed the user-data-dir and reinstalled the extension

Thanks. Unfortunately, this is not a mass-market solution. 🙈

Do you remember whether the error message "pagejs missing" was printed when the issue happened?

@ayasechan
Copy link

ayasechan commented Jun 15, 2022

yes


I often start chrome with different --user-data-dir parameters
Strangely, this problem doesn't occur in some environments (other command line arguments are the same)
So I still have an environment where I can reproduce the problem


error message
alt

@langren1353
Copy link

same problem.

OS:win
Chrome:Chromium 86.0.4240.198
TM Version:4.18.6164
When:Beta Auto Update

After reboot win system and the problem still exists.

Console Log:
content.js:60 Uncaught (in promise) pagejs missing

@simlu
Copy link

simlu commented Jun 15, 2022

Same issue here. I guess time to reinstall the extension! And yes, I get the pagejs missing error as well

@simlu
Copy link

simlu commented Jun 15, 2022

Ok that fixed it. So for anyone looking for a quick solution, this is it:

  • First back up your current data (!!!)
  • Remove extension
  • Re-add extension
  • Import back up data

The pagejs missing error is gone and all works as expected!

@derjanb
Copy link
Member

derjanb commented Jun 15, 2022

Should be fixed at 4.18.6165 (in review|crx)

Chrome/Edge users, please download the crx file linked above and drag and drop it to the extensions page chrome://extensions.

Since I never seen this issue after a browser restart, can someone please verify that the fix works. Thanks.

@langren1353
Copy link

Should be fixed at 4.18.6165 (in review|crx)

Chrome/Edge users, please download the crx file linked above and drag and drop it to the extensions page chrome://extensions.

Since I never seen this issue after a browser restart, can someone please verify that the fix works. Thanks.

after update 4.18.6165 , it works now, problem resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants