+budd-rdc Posted March 28, 2006 Share Posted March 28, 2006 It seems cache pages with high numbers of photos in the gallery will cause virtual memory to run out on a PC when "view them all on one page" option for logs is used. This has happened to me before, but my workaround was to not do this when the gallery count was high. I tried to look at all the logs for Project APE Mission 9 just now, and before all the images were loaded, my Windows PC gave me a warning about running low on virtual memory. I don't want to workaround this one - I enjoy reading the logs and viewing the images for this cache. I figure this depends on the configuration of each person's PC, but more people will run into this in the future, since the number logs and the photos will continually increase. Link to comment
+sbell111 Posted March 28, 2006 Share Posted March 28, 2006 I'm no tech guy, but perhaps a memory upgrade would help. Link to comment
+budd-rdc Posted March 28, 2006 Author Share Posted March 28, 2006 I'm no tech guy, but perhaps a memory upgrade would help. Yup, a memory upgrade would solve the problem for me, at least temporarily. I'm watching the bandwidth monitor on my PC, and the network sure gets busy when all the images are being loaded - wonder if this is putting any load on the Groundspeak image servers? Link to comment
+klossner Posted March 29, 2006 Share Posted March 29, 2006 Try turning off Javascript before loading the cache page. Link to comment
+The Leprechauns Posted March 29, 2006 Share Posted March 29, 2006 Want a sure-fire way to freeze your computer up? Open an archived locationless cache page, one of the ones with 1500 logs, each with a picture or two. Click on "show all logs." Link to comment
+alexrudd Posted March 30, 2006 Share Posted March 30, 2006 Then use the ReloadEvery extension for FX, and set it to refresh the page every second. @budd-rdc: It's not "leaking" virtual memory, just using it. If you were to open up all those pictures in Photoshop you'd get the same thing. Once your computer runs out of RAM, it starts moving data to the hard drive, which Windows calls "virtual memory." Since the hard drive is much slower than RAM, your computer slows down. Link to comment
+budd-rdc Posted March 30, 2006 Author Share Posted March 30, 2006 Thanks for the pointers, suggestions, and escalations (viewing LC pages ). Turning off Javascript is probably the best suggestion for a workaround - I'll do that, thanks. I didn't imply or mention memory leaks with this problem, just excessive use of OS's resources. The excessive disk swapping had long occured before the Windows' "running low on virtual memory" warning popped up. The bandwidth could have been better used for stuff OTHER than loading images I might not view. I didn't comment when autoloading images features were first introduced, but I'm pointing this problem out as a possible drawback. Link to comment
Recommended Posts