Reviews for Tampermonkey
Tampermonkey by Jan Biniok
4,772 reviews
- Rated 5 out of 5by yncncn, 6 months ago
- Rated 5 out of 5by WhiteGive47, 6 months ago
- Rated 1 out of 5by Firefox user 14461240, 6 months agoПоследняя версия съедает всю память и нагружает процессор на 100%. Раньше такого не было, а теперь браузером с этим расширением просто невозможно пользоваться.
- Rated 5 out of 5by Firefox user 18206589, 6 months ago
- Rated 5 out of 5by TFx, 6 months ago
- Rated 5 out of 5by wloving, 6 months ago
- Rated 5 out of 5by plague, 6 months ago
- Rated 1 out of 5by άƈεƥ, 6 months ago
- Rated 5 out of 5by Firefox user 18199441, 6 months ago
- Rated 1 out of 5by Bakajzon, 6 months agoNot open-source but pretend to be(GitHub code never updates)
Developer response
posted 6 months agoThe 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." - Rated 2 out of 5by boozelo, 6 months agocan 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=offDeveloper response
posted 6 months agoPlease 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. - Rated 4 out of 5by Ghis1964, 6 months agoBreaks 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 👍 - Rated 5 out of 5by Aero, 7 months ago
- Rated 5 out of 5by 下雨谁为你撑伞, 7 months ago
- Rated 5 out of 5by Adimar, 7 months ago
- Rated 5 out of 5by Firefox user 12337062, 7 months agoI also have memory leak (v5.0) and crashes. I not use "Never remember history" or "permanent private browsing". Plz fix it
Developer response
posted 6 months agoPlease 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. - Rated 2 out of 5by Flush, 7 months agoAfter 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!Developer response
posted 7 months agoDo you have the "Never remember history" or "permanent private browsing" mode enabled? - Rated 3 out of 5by NameOfMyDisplay, 7 months agoAfter 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.
Developer response
posted 7 months ago👍
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 - Rated 5 out of 5by Firefox user 17768444, 7 months ago
- Rated 5 out of 5by luizhrios, 7 months ago
- Rated 5 out of 5by aming, 7 months ago
- Rated 2 out of 5by jg-staffel, 7 months agoLatest 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".Developer response
posted 7 months agoDo you have the "Never remember history" or "permanent private browsing" mode enabled? - Rated 5 out of 5by Firefox user 16707047, 7 months agoLatest update causes FF to consume more and more ram until it becomes unresponsive and eventually crashes.
Developer response
posted 7 months agoI'm working on a fix. Sorry for any inconvenience.
https://github.com/Tampermonkey/tampermonkey/issues/1921 - Rated 1 out of 5by Janky, 7 months ago