I got a complaint from Rick that pages are running slowly, specifically on this journal page. At first, I suspected that the problem was the recent Flash 8.5 beta which has a documented memory leak, but it turns out he's using Flash 8.0.22 and IE 6, which should be pretty solid leak-wise.

According to Rick, if you bring up this journal page and let it sit, it gets slower and slower.

There's a lot of active content on top of this page, specifically seven Flash animations. Only three of those animations, though, should be taking up any CPU (the three that you see moving right now). The others, specifically the "coming soon" placeholders and the dopey theme-player, should just be sitting quietly.

Rick suspects it's Gamedev's &#106avascript that's bogging things down and not my Flash stuff. This could probably be borne out by looking at other journals without any active content. But if there's no active content, there's really little to tell you that a page is being a hog.<br><br><br>I had always planned to make the stuff up there "lighter" when I get a chance, slowing down the framerate or maybe even making 'em animated GIF files or even just static pictures, but I want to make sure that it'll actually make a difference.<br><br>Is anyone else getting the impression that the journal pages and/or my page in particular is a browser-hog?<br><br><br>Also note that he's reading this page directly on www.gamedev.net. You can read this page from my stuff www.thecodezone.com (which just floating-frames this page and adds yet another layer of complexity to the mix), but he did confirm that there's nothing framing gamedev when the page runs poorly, so there's something right here on this page that's hogging up the works.<br><br>I can always shut off my silly header up there just to see if that clears things up, but I'm gonna solicit other ideas first. Anyone?<div> </div>