Crash Report [@ npswf32_11_2_202_61.dll@0x19e5f5 ]
Over 1400 crash reports.
Build .61 seems to be very unstable:
I think you should stop to deliver build .61
This issue seems like a bug related with hardware accelerated video loading on Windows XP. If possible, I would find out disabling HW accelation in settings stop causing the crash that people are seeing.
it does not.
Memory usage sky rockets and much of it does not get freed with certain media.
Mass Particles test quickly took the plugin container to 800MB
with the release version of flash it was 500MB, and dropped back to 60MB when the applet was closed.
Dailymotion video's usually eat up 150-200MB (they seem to keep the video in memory more than other players) and closing the player does not free this memory back, unlike the release version which seems to manage its memory usage much better. Mozilla actually only recently fixed a bug where plugincontainer was failing to release memory in Firefox 8, but this has only returned with the changing of the flash plugin.
Usually loading 3-4 12 minute long Dailymotion video's takes it up to 800MB used, but closing them all since the update mentioned above would take it back down to 60, or at the best of times, 45MB
with the beta, doing this opens up the same amount of memory, but it only drops back to 650MB usage.
Crash bug (#3020027/internal) is under investiation right now.
Memory usage bug (#3025007/public, #3044908/internal) is not related with above bug. It was closed as fact of life. The new archtechture for multi thread video decoding require more memory usage than before based on engineer's analysis.
It was closed as fact of life.
What a load of crap.
Usage DURING playback, sure. thats fine.
Continuing to use that memory after all applets are closed. IS NOT ACCEPTABLE
Maybe learn how to read a bloody bug report adobe.
I'll be filing a bug on bugzilla to have Flash 11.2 blocked as it conflicts with memshrink otherwise.
Europe, Middle East and Africa