HTML5 webGL memory leak
Posted: Tue Mar 06, 2012 9:54 pm
Hello,
It appears to me that there is a memory problem with the HTML5 webGL player (which affects firefox, and chrome at the moment). If you have a tour that has a hotspot or several hotspots that allow navigation between the panoramas, and you use anypano.xml as the url (which will cause the pano to switch without reloading the whole page), the memory allocated for the browser grows for every pano switch. I can get up to around 3 GB before the browser crashes.
This would not be a huge problem on a desktop, but a handheld device would be a little more challenged to handle this(imo). I don't know if anyone has noticed this problem. This problem appears on both Mac and PC platforms. I am unsure as to how to confirm on the handheld device.
Burley
It appears to me that there is a memory problem with the HTML5 webGL player (which affects firefox, and chrome at the moment). If you have a tour that has a hotspot or several hotspots that allow navigation between the panoramas, and you use anypano.xml as the url (which will cause the pano to switch without reloading the whole page), the memory allocated for the browser grows for every pano switch. I can get up to around 3 GB before the browser crashes.
This would not be a huge problem on a desktop, but a handheld device would be a little more challenged to handle this(imo). I don't know if anyone has noticed this problem. This problem appears on both Mac and PC platforms. I am unsure as to how to confirm on the handheld device.
Burley