We're seeing a memory leak starting in Flash Player 25 ActiveX and continuing through the latest (Flash Player 30 ActiveX). Flash Player 24 ActiveX had no such issue. We created a test .html to show it. It simply loops through playing two different shockwave files. Details can be found in Tracker
Copy link to clipboard
Thanks for the report. I'll escalate it to the team for investigation.
I have a couple recommendations for workarounds, instead of swapping out the element in the DOM:
Thanks, we've got someone looking at it.
Thanks. Are they still looking into it?
Yes, it's still open. I was hoping for a quick win from automated analysis, but it didn't happen. It's a nuanced problem, and because it takes hours or days to get a single result, it's going to move slowly. Realistically, we're months out from shipping a fix to end-users.
Just to set expectations, because of the nature of the fix (it's a complex problem in high-risk/high-importance code), we're probably going to want to target a quarterly major-version release to ensure that it gets adequate exposure to the beta audience.
Thanks for the feedback about how long it might take. From your comments, can I assume that you have been able to replicate the same issue with the test programs provided?
I could give you a random guess, but that's probably not helpful. It will be measured in months. The next major release is September, and we're already in the endgame for that. The following major release would be December. If it's a low-risk thing, we might be able to land it in an intermediate patch release. It's entirely situation dependent and I won't have enough data to judge until we know what the fix is.
Thanks for the information about how long it may take to fix. At this point, though, we're just wondering if you were able to re-create the issue and confirmed it was a problem?
We're able to reproduce it and are investigating.
Thanks. Have you determined whether this will be part of an intermediate patch release or will be part of a major release?
Once we have a fix, we'll figure out what train it will leave on.
Releases ship monthly. Quarterly major releases get more exposure to the beta audience than the intermediate releases do.
If it's a simple low-risk thing, then we'd just put it on the next train. If it's complicated, we'll probably aim for a quarterly major release to maximize the potential that problems get discovered before they ship.
Hi, just wondering if there's been any progress over the last couple months.
Hi, is there any status on when a fix may be released for this issue? Thanks.
did you try the last version 184.108.40.206?
I would prefer to wait until confirmation comes from Adobe since they were able to reproduce the issue.
I have version 220.127.116.11, and if anything, the problem has gotten much worse!