Megazine 3 v 2.0 Ram issue

[Darkpagan]

Hi All,

Firstly hats off to Florian for creating this beautiful script.

The thing I would like to point out is that I have created in v2.0 a book with 86 pages (swf), all look fantastic, the complete book works like a dream, but... yes there always a but... the longer I leave this book running within the browser, and the more I click, the more ram it eats up and does not unload it...

I was just wondering if this is a general "feature"?

What I also forget to say is that I am looking at this via the console and the ram just keeps on increasing...

All the best

[hnuecke]

What version are you using?
There are RAM leak problems with Flash. Those should be addressed and "creatively" solved now.
In both versions: v1.38 and v2.0.0

The release candidates of v2.0.0 also had leaks in some plugins. All known ones should be solved with the latest release.
But there is risk something still is "hidden" somewhere, we did not catch.

So it definetely is not a feature ;-)
The more precise information we get (version number, plugins used, screen shots, ...) the faster and better we can address those problems.

We plan a v2.0.1 update for this coming week end (Nov 8, 2009), and there still is a chance to address such problems if we know in time!

Thanks for your support

[Darkpagan]

Hi there,

Thanks for the quick reply..

I am currently using Megazine 3 v2.0 (the latest). 

Plugins are:

slideshow (1.0.1)
  keyboardnavigation (1.0.0)
  elementids (1.0.0)
  anchors (1.0.3)
  options (1.0.1)
  gallery (1.0.5)
  password (1.0.1)
  backgroundsounds (1.0.0)
  links (1.0.1)
  navigationbar (1.0.2)
  batchpages (1.0.1)
  titles (1.0.0)
  javascript (1.0.1)
  overlays (1.0.1)
  swfaddress (1.0.0)

I have 40 pages in there that are all converted to swf files and amount to 32MB, the page starts with 128MB and increases no matter if I go forward or backwards

Currently after flipping 5 pages I get in the console

Memory Used: 265355264 (~253mb)

I have no other application open...

System: os=Windows XP; language=de; codepage=Unicode; time=Wed Nov 4 16:30:00 GMT+0100 2009; playerVersion=WIN 10,0,2,54; playerIsDebugger=true

[Florian Nücke]

Are the SWFs doing something like adding themselves as listeners somewhere "outside" (stage, megazine, ...), use timers or something like that?

PS: just had a though triggered by this thread. Do you have the check in there to only activate playback if the page is visible? If so, see link.

[Darkpagan]

Hi there,

It does seem all the pages that are loaded / unloaded are always listening. What disturbs me slightly is that this is not just for SWF files within the MegaZine but anything in general, i.e. jpgs etc when you also have a hires included.

I have no clue why this is doing this considering when looking at the code, there should be no need for it to be doing this.

For me personally  is not a big issue since I have over 6GB ram, but when you think of a user who has still only 1024 then issues will definately occur and the browsers will start to freeze up.

If you have any ideas as in to why this is happening, it would be greatly appreciated...

Once more great work on this project, it is just the best thing I have seen in years...

[Florian Nücke]

This is obviously a big concern, the unloading is in there specifically for the reason of not using that much RAM

Could you please check if this also happens if there are no plugins loaded? Might be a glitch in one of them (if you're saying hires can cause this, most likely the gallery plugin). Although I thought I had fixed all leaks before the first release...

[Darkpagan]

Hi There,

I unloaded all the plugins and yes this seems to be part of the issue. Since the ram did not increase as much as before, but still it is constantly increasing and not decreasing.

Kind regards

[Florian Nücke]

Try giving 2.0.1 a go (and clear the cache), see how that works. As I didn't really do anything major in the references / listeners / other memory blocking related areas I don't think it'll change much. A test case zip would be highly appreciated in that case.