Memory Overload? Firefox crashes after 7th click of the "------->" button in image gallery, works fine in Chrome, I.E., Opera

8 wótegrona
1 ma toś ten problem
4 naglědy
Slědne wótegrono wót jscher2000 - Support Volunteer

pśed 9 lětami

26.4.15 15:34

My site has high resolution images in each gallery, average size is about 3.5Mb per each image. After the 7th click of the next button "-------->" or even the 7th click of the random button "RANDOM", all I get is the loading circle spinning forever, the next image will not load.

All galleries works fine in other browsers.

Not sure if this is a refresh issue or a memory overload or what is happening. I have tested this on several different computers with the same effect. Maybe there is a limit on the amount of cache size?

If anyone could test it on their end to verify that the issue is happening that would be cool.

Go to http://www.fantasy18s.com/free/a-gallery/ashley/ and press the next button "--------->" 7 times, allowing each image to fully load. It should crash on the 7th click.

Here is a link to the custom.js file that controls the next button:

http://www.fantasy18s.com/js/custom.js

Thank you for any input.

My site has high resolution images in each gallery, average size is about 3.5Mb per each image. After the 7th click of the next button "-------->" or even the 7th click of the random button "RANDOM", all I get is the loading circle spinning forever, the next image will not load. All galleries works fine in other browsers. Not sure if this is a refresh issue or a memory overload or what is happening. I have tested this on several different computers with the same effect. Maybe there is a limit on the amount of cache size? If anyone could test it on their end to verify that the issue is happening that would be cool. Go to http://www.fantasy18s.com/free/a-gallery/ashley/ and press the next button "--------->" 7 times, allowing each image to fully load. It should crash on the 7th click. Here is a link to the custom.js file that controls the next button: http://www.fantasy18s.com/js/custom.js Thank you for any input.

Answer 1 · 2015-04-26 15:34:21

jscher2000 - Support Volunteer

Top 10 Contributor

26.4.15 16:00

When Firefox crashes, it usually records information about what was happening at that moment. You often will see the Mozilla Crash Reporter dialog come up. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the last section of the support article "Firefox Crashes" for steps to get those crash IDs, and then post some of the recent ones here.

If, on the other hand, you are getting the Windows crash dialog, it's possible we won't have much more information to go on...

Answer 2 · 2015-04-26 15:34:21

jscher2000 - Support Volunteer

Top 10 Contributor

26.4.15 16:05

I think it crashed after 3 images for me, but I had 19 other windows and over 90 tabs open at the time.

https://crash-stats.mozilla.com/report/index/78751b66-357a-4509-9937-af59f2150427

Answer 3 · 2015-04-26 15:34:21

jscher2000 - Support Volunteer

Top 10 Contributor

26.4.15 16:12

According to bug reports linked to the crash report, there is some speculation that this will be fixed in Firefox 38, currently available as Firefox Beta. However, the currently available beta still shows a high incidence of this crash signature, so I wouldn't rush to try it just yet.

Answer 4 · 2015-04-26 15:34:21

Fantasy18s.com Pšašaŕ

26.4.15 16:30

Man, that was quick.

Thank you jscher2000!

Sounds like good news to me.

Must be some kind of memory issue.

Answer 5 · 2015-04-26 15:34:21

Fantasy18s.com Pšašaŕ

26.4.15 16:39

And I forgot to say no, I am not getting the Windows crash dialog. The circle that spins forever is from http://www.fantasy18s.com and inside of Firefox.

I have the current version installed.

Thanks again!

Answer 6 · 2015-04-26 15:34:21

jscher2000 - Support Volunteer

Top 10 Contributor

27.4.15 15:06

I'm not going back to the site. 8-)

Could you look for crash report ID's on the about:crashes page as described in the last section of "Troubleshoot Firefox crashes (closing or quitting unexpectedly)"? Those may shed additional light over the one I posted yesterday.