Hi Steve,
Thanks for getting back to me. I've been working on this problem since yesterday, so far to no avail. It seems like for different computers it happens always, sometimes, or never, but we have yet to narrow down the root cause. I'm glad to hear yours is working now, but please let me know if it happens again. We're going to keep hammering away at this, but here's what we know so far.
- Older versions of BioGPS are also triggering this problem, even from much further back in time, long before this bug was first seen.
- Oddly enough, this is not triggered by JavaScript, but somehow by CSS. Only by stripping out every single CSS file can we prevent the "always affected" computers from getting the CPU spike. Combined with the above, this leads us to believe it hasn't been caused by a change to the BioGPS code.
- Win XP/Vista/7 and Mac OS X are all affected.
- No Firefox plugins or extensions have so far been singled out. We're seeing this across a wide range of installations.
- Many Firefox users have been complaining online about the marked decrease in performance after upgrading from 3.5.2 to 3.5.3. However that's clearly not the only factor at work here, since many other 3.5.3 users are not seeing this problem.
We're running out of avenues to explore, but will keep at it. Our best bet right now is to find other affected users so we can gather more data. Anyone else reading this thread, take note. If you get a CPU spike while loading any BioGPS page, please let us know.
Thanks!
-Marc
________________________________
From: Steve Grubb <
steve...@gmail.com>
Date: Mon, 19 Oct 2009 13:15:17 -0700
To: Marc Leglise <
mleg...@gnf.org>
Subject: Re: [BioGPS] hangs when viewing a gene report - firefox 3.5.3
Hello Marc,
OS is Win XP ... should be up to date w/ patches etc.
Plugins - see attached screen shot of a list of my plugins.
I do have a bioGPS acct ("********") but didn't explicitly log in for the session when I got the problem.
Just now in trying to reproduce the problem I couldn't get the race condition to occur, for that same gene that it did earlier, and for a different gene. Maybe you've fixed the problem.
Steve