Recently, I used flash to create a 3D Modeling object with a 360 rotation display. Due to time constraints, I used the traditional image sequence replacement method.ProgramAlgorithmVery simple, memory usage is terrible (because of the smoothness of the operation, the entire image sequence needs to be loaded into the memory first, as you can imagine ...)
Due to excessive attention to memory usage, I found an interesting phenomenon (the focus of this article ): when the image sequence is scaled to half (scalex <= 0.5 & scaley <= 0.5), and then the image is replaced, the memory is inexplicably increased, if scale remains above 60%, there will be no such "flexibility" problem.
I also made a special round on the Internet. I was very satisfied with the results of other cases about this type of FLASH application. Most of them did not notice this problem, indicating that my insights are extraordinary.
In other words, this is not a matter of technical content, because the program we write is not a problem. The problem lies in Flash Player, and we hope that people in the same channel will be aware of this problem.
I tested two versions of Flash Player, 9.0.151.0 and 10.0.12.36. They are the same as what they do .....