and I don't know the code very well either, But the problem to be said below is indeed a very fatal problem, The only reason is the bug in the Tampermonkey container itself. I have tested/verified/compared repeatedly, and I am pretty sure that it has nothing to do with the URL page or the script code.The URL page and script for the test are provided below, just as an example, In fact, I personally think that there is no problem with the page and the script code itself, because this problem can be encountered on many pages.This fatal problem exists in both the Tampermonkey stable version and the beta version (to be exact, it should have existed for at least 1 year).can skip this floor and look directly at the test example below and the test comparison of Violentmonkey : The above two problems should be directly related. On some pages, scripts cannot be excluded( // at all, even the script is disabled, and even delete to the trash/recycle-bin, still cannot be ruled out. On some pages, it will cause a significant performance drop (very high CPU-usage), and some even crash (it takes ⩾8s~90s to complete load ), during this period, other normal pages will also fail to open. Sys: Win10、 Chromium80-89 (tested+verified) 、Tampermonkey all versions(stable&beta) (at least 1 year) □ 2 fatal problems caused by using Tampermonkey as UserJS/scripts container :
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |