Ok, so it's very specific to BitmapData objects, and even in Grant's
example, it's because he's using a temporary variable which isn't
getting cleaned up, and he has the solution (which IS the solution) to
hold on to the reference to dispose of it later.
The person who posted on the second link
he was able to publish as 7, so he's having some other issue and I'm
willing to bank that he is experiencing memory waste (a leak is
different) ...
No: the flash player is able to correctly delete the memory when I
minimize then maximize the window. If I was still somehow holding on to
a
I've just downloaded the Adobe Flash 9 Public alpha and used it to compile
one of my old kiosk
projects. As far as I can see it has none of memory leak issues which
affected Flash 8 and stopped
it being suitable for kiosks. This is great
This is very interesting. Is it just a matter of
I have no idea what memory leak issues you're talking about with the
Flash player. I've created a few applications that were designed to run
for days and even weeks at a time without a restart and I was able to
eliminate all memory leak and memory waste issues with Flash 6, 7 and 8
with careful
4 matches
Mail list logo
