Skip navigation
Currently Being Moderated

Crash Reports [@ npswf32_11_2_202_61.dll@... ] - Stop delivering build .61

Nov 7, 2011 1:17 PM

Crash Report [@ npswf32_11_2_202_61.dll@0x19e5f5 ]

 

Over 1400 crash reports.

 

https://bugzilla.mozilla.org/show_bug.cgi?id=700364

 

Update:

Build .61 seems to be very unstable:

npswf32_11_2_202_61.dll

 

I think you should stop to deliver build .61

 
Replies
  • Currently Being Moderated
    Nov 7, 2011 3:51 PM   in reply to MrX1980

    MrX1980,

     

    Thank you for your feedback. We are looking into this issue right now.

     

    thanks,

     

    Hitomi

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 8, 2011 11:40 AM   in reply to Hitomi Kudo

    its got a memory leak which causes plugin container to suck up a crap tonne of memory.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 8, 2011 12:47 PM   in reply to Squall_Leonhart69r

    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.

     

    thanks,

     

    Hitomi

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 8, 2011 9:39 PM   in reply to Hitomi Kudo

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 10, 2011 1:53 AM   in reply to Squall_Leonhart69r
     
    |
    Mark as:
  • Currently Being Moderated
    Nov 21, 2011 11:26 AM   in reply to MrX1980

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 21, 2011 12:52 PM   in reply to Hitomi Kudo

    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.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points