You described the problem as just starting, and I see the large footprint across multiple Flash Player versions shipped over the last year in multiple browsers, so it's probably not a change in Flash Player. It could be that garbage collection isn't being triggered yet because you have a lot of RAM available however, if your system is swapping memory to disk because it's low on RAM (I'm assuming that this is what you're seeing when you experience the performance problem, as a larger memory would otherwise represent a lot of cached graphic assets, which would generally improve performance), we should have been garbage collecting before that. Flash Player has automatic garbage collection which is triggered when a percentage of your available memory is reached. I do *not* see the large footprint on Mac. I also see the large memory footprint (500-800MB) on Firefox and Chrome on Wnidows. I walked all the way back to Flash Player 11.9.900.170 and I see the large memory footprint across all versions, and immediately on load.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |