I don't think it is specific to Yahoo mail, but just a tab I usually keep open. The leak occurs throughout the day with various tabs open. Sometimes it is from the Sirius Satellite player (flash based) or the Amazon AWS dashboard (also flash based).
As I said before, it happens on two separate computers (work & home) with similar specs but not identical. Similarities are W7 64bit, IE 9 (32 bit version since some plugins such as the Yahoo toolbar don't work on the 64 bit version).
Thanks for looking into it. If there is anything else I can provide please let me know.
Win7 Enterprise x64, Service Pack 1, MSIE 9.0.8112.16421 32-bit with Flash Player 11.3.300.257.
I used perfmon to track memory usage, and saw no significant increase or spike over a 24-hour period.
I'm not disputing that you're experiencing a memory leak, but I'm not seeing it with Yahoo mail. I'm happy to keep looking if you have other suspects.
Can you try one more thing for me? Same set up, but install the Yahoo Toolbar...
In my effort to pin down the problem I have uninstalled the Yahoo Toolbar on my work computer and it *seems* that the issue has gone away (so far at least - I'll keep running in this scenario to check it).
So it would seem that if I uninstall flash (or disable the Shockwave Flash Object add on) and keep Yahoo Toolbar installed, the memory issue does not occur.
So far, with Flash installed (Shockwave Flash Object add on enabled) the memory issue does not occur.
with both Flash & Yahoo Toolbar I see the memory consumption issue which results in the grey icon for flash videos.
Again, this is very preliminary for me and I might be down the wrong path, but it looks promising so far...
Yeah, I was having a hard time installing it directly from the Yahoo website. I finally searched for it in the add-on manager and was able to install it there.
I'm seeing a really slow increase with Yahoo Mail and Youtube windows open, but it also looks like it cleans up periodically. I'm going to leave it running overnight and see where things are in the morning.
Okay, this is the weirdest problem I've seen in quite a while, but I'm successfully able to reproduce.
I opened the following bug on it to get it investigated:
Well great! I'm glad we were able to hunt down the scenario and reproduce... Good thing I come from a long background of QA and Development!
Thanks for taking the time to reproduce it, and I hope it will be addressed soon since this affects every computer I use since Yahoo Toolbar is my primary toolbar.
Can you confirm your ram - Cp6 needs 4gb compared to Cp .5. which needed 2gb!. (Interestingly Adobe have left off windows vista for Cp 5.5)
Are you using IE 64 bit or IE 32 bit ?
If 64 bit have you installed the 64 bits flash player?
Check your version here
Windows for 5.5
• 1GHz or faster processor • Microsoft ® Windows® XP with Service Pack 2 (Service Pack 3 recommended); Windows Vista® Home Premium, Business, Ultimate, or Enterprise with Service Pack 1; or Windows 7 • 1GB minimum RAM (2GB recommended)
Windows version 6
- 1 GHz or faster processor Intel® Pentium® 4, Intel Centrino®, Intel Xeon®, or Intel Core™ Duo (or compatible) processor
- Microsoft® Windows XP with Service Pack 3; or Windows 7 with Service Pack 1
- 2GB minimum RAM (4GB recommended)
I have a memory leak issue on www.bloomberg.com using 32- and 64-bit IE 9 on 64-bit Windows 7. The website reloads automatically at time intervals; each time, IE takes another 85 MB of memory. I have seen IE memory usage as high as 2.5 GB!
This problem does not occur when the Flash add-on is disabled, or on Firefox.
The same problem occurs on my Dell Latitude and Lenovo ThinkPad laptops. The machines have similar Windows and IE configurations.
I am using Flash 11.3.300.270, and I have installed the latest updates for IE and Windows.
Thanks for looking at this issue!
My first hunch would be that this could be actionscript related, and possibly a problem with the bloomberg site. However, if this does not occur on Firefox (or Chrome) then we might be dealing with something else. Could you please open a bug on this at bugbase.adobe.com so we can investigate further?
PS. I tried this out using the same config but IE leveled out at 210mb and didn't grow further (I left the browser alone for about 30 minutes, also tried refreshing manually 10 times or so.)
Just my five cents. Our team faced with similar issue in IE9 when after reload browser no memory released. Our investigations resulted that it is somewhere in "swfobjects.js" that is, JScript is not releasing SWF object in IE.
After struggling with it, we ultimately dropped using "history.js" and the issue went away.
This issue seems similar.
I have the identical problem with Win 7, 64 bit + IE8, 32 bit. Four to six tabs open, one of them is Yahoo Mail, and it's just a matter of time before I encounter the Adobe GCOD (Grey Circle of Death) signaling a shortage of memory available to the Flash player. I have a couple of add-ons including two or three toolbars, and have come to the conclusion that it's either:
1. some glitchy interaction between one of my add-ons + Flash
2. some glitchy interaction between one of my add-ons + the Yahoo Mail website
3. some glitchy interaction between Flash + the Yahoo Mail website
I've never once experienced this problem in Firefox, though I typically access Yahoo Mail using IE, and have less add-ons in Firefox. I've tried all the usual suspects, resetting IE to default settings, reinstalling IE, reinstalling Flash, Shockwave, Java... I assume it's not #3 because there must be many people successfully running the Flash player in conjunction with Yahoo Mail. I wish there some kind of software that could specifically pinpoint problems encountered when browsing in IE. One solution would be test each add-on separately to try to pinpoint the problem, but sometimes it may take 1 or 2 hours for the problem to occur, so it's somewhat lengthy to test each add-on... BTW, I'm focusing on Yahoo Mail, but perhaps a similar website that uses flash/scripting/ajax might bring about the same endgame.
Unfortunately Flash has had a memory bug since CS3 as far as I know the problem has never been fixed. We are up to CS6 now and the bug remains but now instead of stopping at the 2GB limit it just keeps getting bigger and bigger as Internet Explorer now has a 64-bit version. I feel sorry for the companies like in the picture above. Great games but hug memory bugs. They will probably go bust if you don't do something soon. Please fix the memory leak. Even after shutting the game window 2 gig remains in the temp area. If I clear everything from the tool area it goes back to normal.
Illustrator also has a line drawing bug where the whole screen goes white when drawing a line past the artboard. The autoscroll kicks in but you can't see the line being drawn. Why do't you work on these problems? 3 full suites later and no change. Just get rid of the bugs instead of adding more features. It seems silly having more options but not being able to draw a line larger than the screen area without a propper refresh.
For me the number of tabs does not make a difference. Using IE9 & Yahoo mail is the common theme. I will check if flash makes a difference but I went back to IE8 and did not have a problem.
I get a memory leak with yahoo (so maybe with flash) on all the browsersthat I use (IE, Firefox, Chrome) but the main difference is that in IE9 the performance is too slow when editing emails. IE8 does not have the performance problem though memory does leak a bit. I am running Win7 latest services packs.
For me it does not take very long for the memory to jump to 600+ I kill IE9 several times a day.
I have recently installed ie9 again after removing it in september of last year / the only slight improvement with the problem is now I can kill a separate instance of explorer for when yahoo opens it seems to have its own instance - where before all tabs were affected.
Did a cold boot to ensure RAM was clear.
I turned flash off and the only difference was the ram did not climb as fast. Still a problem though. For me the issue seems to be a problem with IE9 in general - problems increase with yahoo.
I applied additional MS updates today so I can not report which fix is making the difference.
Another cold boot
So .. running IE64 - with no yahoo mail and flash turned off - seems to stabalize after growing very slowly.
Turned Shockwave back on .....seemed to be fine.
Ran site with video - big jump in ram but that was to be expected.
Killed video and ram cam back to previous amounts used.
Launched Yahoo - big jump in RAM use but probably due to all the ad's
- with new patches the RAM seems stable - now adding more tabs to see the affect besides an increase in RAM
- 5 tabs open - stable for first 5 min at least.
- opened additional emails. still stable
**** will continue to monitor but the constant gradual growth seems to be gone .... or I have not used the right combination of features that triggers the memory leak.
First, I just wanted to follow up on this thread and let you guys know that we'll continue to look into it. I also want to clarify some player behavior, and provide tips for helping to identify a defect that we can take action on.
Whenever you refresh/reload a tab, the browser should signal to us that our process is being destroyed, at which point we would release all of our resources and shut down. SergeStone's comment above makes it sound like this might not be happening in a particular case. I'm going to build out a few tests this week to explore this in more detail, and I'll follow up with results.
Also, it's worth discussing the difference between memory consumption and memory leaks. Flash Player is designed to consume a percentage of your available memory. If you have a 32-bit machine with 2GB of RAM, we're going to consume a lot less memory than a 64-bit system with 16GB of RAM.
Not all Flash content is authored well. If the ActionScript developer is continuously loading objects into their SWF and never releasing them (a slide-show is a good simplistic example), you'll see a steady usage increase as each new object loads in. You should also see that evenutally, our automatic Garbage Collection process will kick in. Memory will peak out, and then you'll see a short CPU spike as we look at all of the available objects and cull as many unused ones as possible, consumed memory will dip down significantly (as long as we can cull stuff), and then start growing again until the next time GC kicks in. We tend to do this judiciously, as poorly-timed GC can cause games to stutter if it happens when lots of things are moving around on the display and you don't have a lot of available CPU.
If it's our bug, it should be straightforward to fix, and I can follow up to this thread with a beta build for you guys to evaluate once we have one available. In the meantime, it would be interesting to know if you're seeing the problem on our current Beta builds (which is where we would do the work).
Here's a link to the latest Beta download:
Also, the simplest example is the most actionable. If you can find a situation where a site in a single tab reproduces the problem, that's a quick and easy thing to deal with. If the repro case involves opening seven tabs and waiting six hours, someone needs to repeat that over and over, until they can isolate what content experiences the problem and then iterate a bunch more with a debugger attached to try and isolate the root cause. The more complicated the content, the more difficult that is.
Secondly, I wanted to offer some actionable suggestions that you could use now to work around this issue.
- Try Firefox or Chrome. Both of these browsers run Flash Player as a separate process.
- For those of you using Performance Monitor and other tools to measure, you can directly observe the resources used by Flash Player
- For the folks concerned about Bookmarks synchronization, both Firefox and Chrome provide native bookmark syncing and import from IE mechanisms.
- Xmarks is a really nice, free utility that provides cross-browser, cross-platform bookmark synchronization.
- Try Firefox or Chrome. Both of these browsers run Flash Player as a separate process.
Thanks for the update Jeromie - it is very frustrating going through this guessing process - I long for the old days where we could turn on a trace log that profiled the memory hogs and program locations. - it would be nice if something could be adapted for the browsers with out having to load IDE's and perfmon is basically useless when it comes to end user debugging for it is like working with a bunch of black boxes that are usually not the culprits anyways.
I can try to run the different cases you suggest but it would be nice to know a bit more about isolating your application first. Just so I am comparing fairly.
For example - How do I ensure that I have unloaded all of your app without uninstalling and rebooting?
Is there a way to turn on some level of logging? Maybe with the beta version?
My biggest problem seems to be Yahoo Mail - do you have any feedback on this.
What is different with IE8 and 9? I mean 9 become unusable and even with a clean boot there are features in yahoo that do not work in 9 versus using firefox or chrome.
Also - I just loaded some updates and the memory seems to clean up right away unlike before where there was a drop followed growth when I unloaded pages.
Is there a switch that forces garbage collection?
Is there a way to map the memory in such a way as to see what is taken up but not used - sort of like the old days when we would use overlays. - crude I know but I used to run full accounting systems in 28k of RAM. Now I can't load my logo with that much
All the best and thanks for XMarks - you just saved me some work syncing the 3 browsers I am running.
Thanks for your note.
The best way to get traction on the issue you're experiencing with Illustrator is to report it to the Illustrator team.
Their bug reporting form is here:
Their forums are here:
I've found it's particularly effective to file the bug, then post to the forums with a link to the bug. This makes it easy for the person responding to your issue to route it to an engineer (in general, work is conducted and tracked through the bugbase), and the forum post is likely to automatically land in the inboxes of people on the product team who are subscribed to forum notifications.
The more information you can include about your issue, a sample file where it reproduces (unless it happens everywhere), and as much information about your system as possible would be good. Modern versions of most Adobe tools use Hardware Graphics Acceleration, and this drawing issue could be related to your graphics hardware.
Without knowing much about your problem, I'd recommend you update to the latest available drivers for your graphics hardware as a first troubleshooting step. If the problem persists, providing the output of the DirectX Diagnostic Tool will provide the engineering team with enough detailed information on your system configuration to investigate it fully.
To run dxdiag, do the following:
Click Start > type "dxdiag" in the search box and hit Enter
Click Save All Information, and attach it to your bug report
You could also try disabling hardware acceleration to see if this resolves your issue (it would be an interesting data-point for the person triaging your bug report):
Quality Engineering Manager
Flash Runtime - Security
So what I find frustrating is that I submit information almost 4 months ago, that you reproduced and created a defect for, yet nothing beyond that has been done. No updates on the defect, etc... Actually when I look at the defect in your database it doesn't even appear that anyone has taken the time to look at it.
We keep separate internal and external bugbases to maximize productivity on the engineering team. When we have a widespread issue, we'll have hundreds of duplicate bug reports. There's a dedicated team that consolidates and escalates the publicly reported issues to the engineering team.
Issues reported are prioritized by severity, number of users impacted, number of votes received, and the availability of a workaround. We have not fixed this issue yet. I have resurfaced the bug to the engineering team for consideration in the next dot-release. There is a very straightforward workaround at this time, in that you can uninstall Yahoo Toolbar and avoid that particular memory leak.
" I have resurfaced the bug to the engineering team for consideration in the next dot-release."
- Thank you
" There is a very straightforward workaround at this time, in that you can uninstall Yahoo Toolbar and avoid that particular memory leak."
- Actually there are a couple of straightforward workarounds... One being just uninstall Flash...
As an end-user, you can't do anything about when GC happens. As a developer, you can do things to request GC at optimal times during your application's execution, but older content doesn't have that capability, and skill levels and priorities vary between developers.
The reason I'm suggesting Firefox or Chrome for differentiating the behavior is that there is no guessing. With IE, Flash is running in the iexplore.exe process (there's one process for the host browser, and then one for each child tab). There's no way to know whether it's Flash or the Browser eating all that memory (and it's mostly likely some interaction problem between the two).
In Firefox, Flash is running in it's own process (FlashPlayerPlugin_11_x_x_xxx.exe -- there's actually two, one is a broker and one is the child process that does the heavy lifting). You can watch the process directly.
With Chrome, the task monitor proposition is trickier, because all processes are named Chrome.exe, but some of them are the Flash Player plug-in. Fortunately, there's a task manager built into the browser that shows you what plug-ins are running and what resources they're consuming. Just click on the right-most icon (it's a wrench or a menu icon, depending on version) and choose Task Manager. You'll see Plug-in: Shockwave Flash with the amount of memory being consumed.
If you want gory details on the differences between IE8 and IE9, the IE Team has a blog: http://blogs.msdn.com/b/ie/. You'll have to go look around in the archives, though. In general, the rate of change in the browser space has accelerated significantly in the last couple years. Chrome and Mozilla ship feature-bearing releases on 6-week schedules. IE has also made significant improvements to their browsers during that time. Many of these releases make changes to how we interact with those browsers, and we communicate closely with all of the major browser vendors to try and stay ahead of those changes and keep everything working well.
There are some automated tools you can run in the background, like Microsoft's DebugDiag (http://www.microsoft.com/en-us/download/details.aspx?id=26798) -- which can be configured to monitor process and catch memory leaks, but I don't think it's going to catch anything in this instance. If you get the memory back after fully exiting the browser, then it's not really leaking by the strict definition of the term.
If you're not seeing the issue with the latest IE9 and the current Flash Player, I don't want you to spend a bunch of time doing that, and it may have other stability side-effects anyway. If you're really interested, I can write up some directions on how to configure it for IE9, but I don't think it's going to be fruitful in this instance.