It is possible I was holding it wrong. I do not doubt your experience, but it was very easy to write things that leaked memory in Flash, and it was impossible to remove those leaks sometimes. I was part of a project where a lot of effort went into removing references etc and it was still not working. We had to have 2 instances restarting each other. It was a mess. Maybe we can agree those were "bad components".
I blame the runtime. The quality of the code was good. It was not normal.
A few sources of people complaining about the same, some from hn with the same solution I had to adopt, some from CVE, some from users:
I blame the runtime. The quality of the code was good. It was not normal.
A few sources of people complaining about the same, some from hn with the same solution I had to adopt, some from CVE, some from users:
- https://community.adobe.com/questions-638/flash-player-23-24...
- https://advisories.checkpoint.com/defense/advisories/public/...
- https://news.ycombinator.com/item?id=45813026
> The memory leaks were so bad that Adobe advised us to just restart the app periodically
- https://blog.gskinner.com/archives/2005/10/major_flash_pla.h...
- https://support.mozilla.org/bm/questions/931671