Shape 5

Hi,
I'm not sure whether to post it here or in the extensions forum, but here it goes.

I've discovered a memory leak on a production site, Lokal-web.dk, almost ready for marketing. The frontpage manages to crash both my Firefox 24 and Chrome (haven't tested IE) when idle. Steps to reproduce:

• Open Chrome, navigate to URL http://lokal-web.dk
• Leave it while monitoring task manager
• Watch used memory increase steady - and crash at last

I think I've located it to the S5 content and image fader v3, because it seems to be stabil whenever I switch it off, and doesn't occur on other pages where the slider isn't present.

I like the transistions with image text and description, so I would rather not replace the slider module with another. Solutions, suggestions?

Best regards,
Claus

Hello,

I just tested this in multiple browsers and my memory was not spiking. It only fluctuated by about .01GB when the slides were changing but never anything above that. We also haven't had any reports of this issue before and the Image and Content Fader has been in production for a very long time.

-Mike

Hi, thanks for trying,

Did you leave it open for a few hours? I ask because I already have tested on 2 different machines from 2 different locations numerous times with the same result. Chrome seems to be the fastest to reach memory limit on both. For the record, I tested with no other panes open.

I did search the forum and noticed that there were no records on this issue, but I figured it were due to the fact that very few people have their frontpage open for so long without activity.

/Claus

Hello,

I just tested this in Chrome for about 45 minutes and my memory still didn't spike at all and the slides still functioned properly. I will see if I have another lower end system to test this on as the one I am on is using the latest and greatest.

-Mike

Just to clarify; it's not CPU-usage - that one spikes as well on slide turns, it's physcal memory usage that increases slowly but consistantly.

I had a dev-friend of mine test on his machine as well - it crashed after 3 hours of monitoring.

Hello,

I had two of our developers test this on their systems for a few hours as well and neither of them had any crashes or increase in memory usage. I would need some more information to determine what would cause this such as:

1) Browser Versions and What Browser It Occurs In
2) System Details
3) Does it occur in J2.5 or J3.0 or both?
4) An error log from a few different systems

-Mike