Ocene za Tampermonkey
Tampermonkey — Jan Biniok
5.186 ocen
- Ocenjeno z 5 od 5— TFx, pred 2 letoma
- Ocenjeno z 5 od 5— wloving, pred 2 letoma
- Ocenjeno z 5 od 5— plague, pred 2 letoma
- Ocenjeno z 1 od 5— άƈεƥ, pred 2 letoma
- Ocenjeno z 5 od 5— Uporabnik Firefoxa 18199441, pred 2 letoma
- Ocenjeno z 1 od 5— Bakajzon, pred 2 letomaNot open-source but pretend to be(GitHub code never updates)
Odgovor razvijalca
objavljeno ob pred 2 letomaThe README clearly states: "This repository contains the source of the Tampermonkey extension up to version 2.9. All newer versions are distributed under a proprietary license." - Ocenjeno z 2 od 5— boozelo, pred 2 letomacan confirm that memory leaks (eats all free memory - up to 50gb ram for 3h), high cpu usage on v.5.
Also pages do not open in new tabs the first time
"Modify existing content security policy"=off, "Never remember history"=off, private=offOdgovor razvijalca
objavljeno ob pred 2 letomaPlease report an issue at GitHub and explain what you're doing while this happens. I double checked the code, used Firefox many hours and can't reproduce. Thanks. - Ocenjeno z 4 od 5— Ghis1964, pred 2 letomaBreaks my user-css-style for twitter. Rolled back to 4.19.0 before witnessing more unwanted issues.
Took me a while before realizing tampermonkey 5.00 was the culprit. Yeah, a while :/
edit 2:
Beta 5.0.6191 had the same issue. (but totally breaks youtube's feed page no matter what)
Settings I ventured in then, and found out that -Modify existing content security policy (CSP) headers = no- instead of -Modify existing content security policy (CSP) headers = yes- fixed my issue 👍 - Ocenjeno z 5 od 5— Aero, pred 2 letoma
- Ocenjeno z 5 od 5— 下雨谁为你撑伞, pred 2 letoma
- Ocenjeno z 5 od 5— Adimar, pred 2 letoma
- Ocenjeno z 1 od 5— Uporabnik Firefoxa 18195760, pred 2 letomaUpdate broke the scripts im using for tumblr
- Ocenjeno z 5 od 5— Uporabnik Firefoxa 12337062, pred 2 letomaI also have memory leak (v5.0) and crashes. I not use "Never remember history" or "permanent private browsing". Plz fix it
Odgovor razvijalca
objavljeno ob pred 2 letomaPlease report an issue at GitHub and explain what you're doing while this happens. I double checked the code, used Firefox many hours and can't reproduce. Thanks. - Ocenjeno z 2 od 5— Flush, pred 2 letomaAfter I updated tampermonkey to 5.0, it's eating my CPU and leaking memory. Had to rollback to 4.19 (Firefox 120.0.1 64-bit)
About Your question. No, I haven't!Odgovor razvijalca
objavljeno ob pred 2 letomaDo you have the "Never remember history" or "permanent private browsing" mode enabled? - Ocenjeno z 3 od 5— NameOfMyDisplay, pred 2 letomaAfter update to 5.0.0 at 102ESR, with RuAdLIst JS Fixes, Yandex maps gave up loading map images. Had to rollback to 4.19.0.
Odgovor razvijalca
objavljeno ob pred 2 letoma👍
Unfortunately this regression wasn't detected by the users of the beta version.
I'm working on a fix. Sorry for any inconvenience.
https://github.com/Tampermonkey/tampermonkey/issues/1921 - Ocenjeno z 5 od 5— 小恶魔, pred 2 letoma
- Ocenjeno z 5 od 5— luizhrios, pred 2 letoma
- Ocenjeno z 5 od 5— aming, pred 2 letoma
- Ocenjeno z 2 od 5— jg-staffel, pred 2 letomaLatest update causes FF to consume 30-90% CPU and eating more and more RAM, that caused lags and in the end full unresponsive.
P.S. No enabled "Never remember history" or "permanent private browsing".Odgovor razvijalca
objavljeno ob pred 2 letomaDo you have the "Never remember history" or "permanent private browsing" mode enabled? - Ocenjeno z 5 od 5— Uporabnik Firefoxa 16707047, pred 2 letomaLatest update causes FF to consume more and more ram until it becomes unresponsive and eventually crashes.
Odgovor razvijalca
objavljeno ob pred 2 letomaI'm working on a fix. Sorry for any inconvenience.
https://github.com/Tampermonkey/tampermonkey/issues/1921 Odgovor razvijalca
objavljeno ob pred 2 letomaPlease downgrade to 4.19 or disable the "don't remember history" setting for now. Sorry for any inconvenience.
https://github.com/Tampermonkey/tampermonkey/issues/1921- Ocenjeno z 5 od 5— Dev, pred 2 letoma
- Ocenjeno z 5 od 5— Gustavo., pred 2 letoma
- Ocenjeno z 5 od 5— Why, pred 2 letoma
- Ocenjeno z 5 od 5— Dan Atkinson, pred 2 letomaEver since I updated the extension last week, a new Google Drive API authorisation tab opens every five minutes for the sync functionality. No matter how often I approve it, it still pops up.
Edit: Developer has responded that it will be resolved. In the meantime, I've turned off sync completely.Odgovor razvijalca
objavljeno ob pred 2 letomaSorry, this is a bug due to the background event page being restarted every 30 seconds if idle. Will be fixed soon. Please downgrade to 4.19.0 in the meanwhile.