Posted by Brad Wood
Sep 26, 2008 04:56:00 UTC
So in the past 3 days I have been trying Flex I've had several out of memory errors that crashed my browser. I don't know if it is my operating system, my browser, Flash in general, or Flex, but it sucks. For the record I am using Windows XP Pro, IE 7, Flash 9, and Flex 3. This is what happens: As I develop, I keep hitting save in Flex Builder, waiting for it to recompile in the background, then Alt-tabbing over to IE and whacking F5 to refresh. Well, over the course of 2 or 3 hours of doing this, the memory usage for iexpolore.exe just keeps climbing and climbing as though there is a memory leak or garbage collection isn't happening.Finally once IE gets close to about 600 to 700 Megs of Ram I hit refresh, and WHAM! First, Flash pops a cute little error box with a stack trace that informs me "Error Code 1000: The system is out of memory." This page on Adobe's site says, "Flash Player needs more memory to compile your code than your system has available. Close some of the applications or processes running on your system." I don't by that. My machine has 3 Gigs of RAM, and up to 1.5 Gigs will still be free when this happens. I don't think closing any applications or processes is going to fix it. The error consistently happens around 700 Megs, so I think there is some internal limit in IE or something. Once I close the Flash error pop up, the entire IE process (including all the other tabs I had open) crashes hard with the little "Do you want to send Microsoft your bank routing numbers?" pop up that I always click "don't send" on. Today I am using Firefox. We'll see how that works for a change. Take that Microsoft.