W dniu niedziela, 28 lutego 2016 01:42:12 UTC+1 użytkownik Daniel Wynalda napisał:
> I notice that old versions of Greasemonkey kept the setValue data in the > area where about:config in firefox could see them. Now they aren't > visible. Are there any tools that can be used to identify what is stored > in the GM_getValue and GM_setValue storage area? I'd like to see if > there's something unique about the data being stored for specific people > (perhaps a runaway loop storing a ton of data or something) > > You are right, I notice the same speed problem when jump form older GM (store data in prefs.js) to new GM (store data in SQLite). I save a lot of data URL for future processing and remember that after update GM then this new storage system was worse. The only positive was not rubbish prefs.js. But really if you have developed a script that works on multiple tabs (in the same time) then all this new Firefox version is "crap", release before 2 o 3 years works better (especially when it comes to UI responsiveness or network operations). Even turn on e10s does not help, what really scares me. -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/d/optout.
