Closed frioux closed 12 years ago
So... I just tested on OS-X and the Firefox 6.0 beta and didn't see this happen. A few questions. 1) What OS? 2) What dotjs version? v0.6 was built with an older version of the SDK so maybe there is an issue there. v0.9 (in the approval queue still) is using latest which is a release candidate for the Addon SDK 1.0. 3) Does it happen even if none of the sites you are on has a .js file for them?
Maybe something in a .js file is triggering this when running it through dotjs context? I am definitely interested in finding out more to try to figure out what's going on.
Thanks!
1) linux (ubuntu) 2) v0.6, I'll try v0.9 after I comment. 3) it doesn't seem like it. Interestingly when I ran into this issue all I had was a blank default.js file
unfortunately it seems like v0.9 suffers from the same issue. I'm gonna replace the blank default.js with a (function(){})() and see if that makes a difference.
Nope, that made it a lot worse :-)
oh well, that helps though. I will try it out on Ubuntu and (hopefully I get the same issue) will try to figure out what it is. :-)
Does this still happen in Firefox 7? hoping not
When I have this addon enabled Firefox consistently pegs one of my two cores. If you can't reproduce let me know and I can add more information.