Images of the Holy Land uses 300MB of RAM by itself
I notice that opening Images of the Holy Land took a lot of time and disk access, so I opened up the task manager.
Before IOTHL is opened:
Then after I open IOTHL, and the image on the page finishes loading:
And then after I close the resource:
Now it must be loading every picture in the resource into memory for this to be happening. Isn't there a better way?
EDIT: It's especially odd since the resource on disk is only 14 MB.
MacBook Pro (2019), ThinkPad E540
Comments
-
Thanks Todd. I've reported this. I also noticed that it doesn't always release the memory after you close the resource, so reported that as well.
0 -
I get a similar response but it is only while it is displaying. If I place a different book over the top of it, moving the tab for IOHL to the back, then the usage promptly drops as well.
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
Melissa Snyder said:
Thanks Todd. I've reported this. I also noticed that it doesn't always release the memory after you close the resource, so reported that as well.
It didn't drop until I did something else like open the library.
MacBook Pro (2019), ThinkPad E540
0 -
Todd Phillips said:
I notice that opening Images of the Holy Land took a lot of time and disk access, so I opened up the task manager.
The "media resources" (resources that have the "Overview" screen of all the graphics) haven't been optimised for memory usage. (Sorry, this is a known issue internally that didn't make it to the Known Issues list. It will probably be fixed in Beta 5. Until then, just don't open two of them at once... [;)])
0 -
Bradley Grainger said:
Until then, just don't open two of them at once...
)You're a funny guy...har har har. [8-|] ( <- microsoft bob)
MacBook Pro (2019), ThinkPad E540
0 -
