On Fri, Feb 26, 2016 at 10:23 AM, Daniel Wynalda <[email protected]> wrote:
> Has the method for saving GM_setValue and GM_getValue data changed in > Greasemonkey? > Yes. Compatibility with multi-process Firefox forced significant changes on our part. No coincidence that the 2.x/3.x barrier is what you've noticed, given the 3.0 release notes ( http://wiki.greasespot.net/Version_history#3.0_2 ). The scripts operate in the child where the content is, but only the parent can read/write from the disk. The forced restriction on the (purely in-memory) preference store also didn't help. > Any suggestions as to what might make GM_getValue and GM_setValue *VERY* > slow on some profiles and not others would be greatly appreciated. ... It > is evident on the machines running slow that the profile is being accessed > on disk over and over again causing significant latency waiting for the > disk to read/write constantly. > You already have more data than we do. Can you find a pattern? Hardware? Operating system and/or version? Etc? We've resorted to moving some of the data out of GM_setValue locations into > localStorage locations and other checks we've just skipped to reduce the > delays. > If localStorage works, why are you not relying on that completely? -- 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.
