-
|
Click on places, wait for map to load, zoom in, zoom in, make sure there aren't loads of pictures stacked (like I see a circle with 5 inside, zoom in), I see round thumbnails, all fine. Debug logs on the server with all GETs/database queries, etc. All of the above is fine and I guess that should be the more intensive part both on the server and browser. Then click on one picture - nothing happens except the browser eating more and more RAM until it runs out. Server log is silent, not much network activity (the server is fine and can serve other clients, only this tab is gone). I took it as a regular "more RAM needed" until I went to 32GB and still not enough. Windows + latest stable Chrome and Firefox were tested. This might be a regression, it used to work (not flawless but it was working some months ago). Large library - Search shows 477k, Places shows 1400 places. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
|
Maybe you had less images months ago? I can imagine that creating the data structure holding 477k images is too much for the current photo viewer. It's can't dynamically load more pictures, so the list is generated upfront (pictures are NOT all loaded upfront). Can you try what happens if you search for a keyword or place? This reduces the number of pictures. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that's the way it works as the map items are loaded once and rendered dynamically. The photo viewer is not part of the map, so its contents are not dynamic. |
Beta Was this translation helpful? Give feedback.
-
|
Tested with 100k images on OSX with just 16 GB of RAM and Google Chrome. Opening the viewer is a bit slow, but definitely not running out of memory. |
Beta Was this translation helpful? Give feedback.
-
|
Obviously we will improve this and a new image viewer is already on our roadmap. It's just that we can't work on everything at the same time. |
Beta Was this translation helpful? Give feedback.
-
|
To get a dynamic picture list, you'd need to get the visible object list from the memory of the map viewer as it depends on the coordinates, viewport size, view angle, and zoom level. |
Beta Was this translation helpful? Give feedback.
-
|
You are also welcome to send a PR with optimized JS code as a temporary workaround until a new viewer is available! |
Beta Was this translation helpful? Give feedback.
Maybe you had less images months ago? I can imagine that creating the data structure holding 477k images is too much for the current photo viewer. It's can't dynamically load more pictures, so the list is generated upfront (pictures are NOT all loaded upfront). Can you try what happens if you search for a keyword or place? This reduces the number of pictures.