When I click on a thumbnail in 2.0.0, the URL changes, but nothing appears. #1043
Replies: 5 comments 1 reply
-
|
Can you try reproducing on the edge tag?
There were a lot of code change since 2.0
…-- Sorry for being brief, sent from my phone.
On Wed, 24 Sept 2025, 15:28 Mark Poncelet, ***@***.***> wrote:
I would love some help, as I've been working on this now for weeks and
just can't figure out what's going on.
I have a big 100,000+ library. After a fresh install of 2.0.0 on the
latest tag, all the initial ingest jobs work great. (I usually skip video
transcoding, though.) Things work perfectly for a bit. Then I will come
back later and click on a thumbnail only to see the URL change but nothing
appear on the screen. Scrolling no longer loads new thumbnails in the
gallery. If I close the browser and then come back, I can scroll through as
many thumbnails as I want, but clicking on any of them causes the same
problem. This is true in Safari and Firefox.
I'm not 100% sure, but I think the problem may start happening after I
ungroup the thumbnails. I remember doing that as the last thing before the
problem most recently happened.
The thing that gets me is that 1.9.5 works great with the same library.
This is a vanilla install straight from the latest tag with no settings
changed from stock. I didn't install nginx, either. I'm stumped.
My environment is a debian VM in Proxmox, with images on a local drive. 2
cores, 8 GiB RAM. This VM is a clone of the one the 1.9.5 instance is
running on, and they're accessing the same directory for image content.
(Different pigallery2 directories, of course.)
Any ideas what I should do?
—
Reply to this email directly, view it on GitHub
<#1043>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZKA5XLFGSQJUHU2QSDPW33UKL6VAVCNFSM6AAAAACHMCBBHOVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYHE2DCMRYGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Also I would need some server and client logs to debug it.
Can you provide those?
…-- Sorry for being brief, sent from my phone.
On Fri, 26 Sept 2025, 10:14 Patrik J. Braun, ***@***.***> wrote:
Can you try reproducing on the edge tag?
There were a lot of code change since 2.0
-- Sorry for being brief, sent from my phone.
On Wed, 24 Sept 2025, 15:28 Mark Poncelet, ***@***.***>
wrote:
> I would love some help, as I've been working on this now for weeks and
> just can't figure out what's going on.
>
> I have a big 100,000+ library. After a fresh install of 2.0.0 on the
> latest tag, all the initial ingest jobs work great. (I usually skip video
> transcoding, though.) Things work perfectly for a bit. Then I will come
> back later and click on a thumbnail only to see the URL change but nothing
> appear on the screen. Scrolling no longer loads new thumbnails in the
> gallery. If I close the browser and then come back, I can scroll through as
> many thumbnails as I want, but clicking on any of them causes the same
> problem. This is true in Safari and Firefox.
>
> I'm not 100% sure, but I think the problem may start happening after I
> ungroup the thumbnails. I remember doing that as the last thing before the
> problem most recently happened.
>
> The thing that gets me is that 1.9.5 works great with the same library.
>
> This is a vanilla install straight from the latest tag with no settings
> changed from stock. I didn't install nginx, either. I'm stumped.
>
> My environment is a debian VM in Proxmox, with images on a local drive. 2
> cores, 8 GiB RAM. This VM is a clone of the one the 1.9.5 instance is
> running on, and they're accessing the same directory for image content.
> (Different pigallery2 directories, of course.)
>
> Any ideas what I should do?
>
> —
> Reply to this email directly, view it on GitHub
> <#1043>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABZKA5XLFGSQJUHU2QSDPW33UKL6VAVCNFSM6AAAAACHMCBBHOVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYHE2DCMRYGA>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
|
I pulled edge-debian-bullseye and started from scratch, indexing a library of over 120k items. I let it convert the images, but disabled the video converting, maps, and faces to save time. I ran into the following error during reindexing: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory So I upped server RAM and added NODE_OPTIONS=--max-old-space-size=8192 to the docker compose. That got me through all the jobs without any material errors. When finished, the gallery loaded just fine. Scrolling the gallery would lazy load new thumbnails nice and fast. Clicking on an image would expand it. There was only one console error, which I always see whenever I load pigallery2: [Error] QuotaExceededError: The quota has been exceeded. — main.5d0165c0a9e176ee.js:3:364542 I get a similar error no matter which version of pigallery2 I run, every time, so I ignore this error. --- Main issue --- On the server logs, I see the initial load of each thumbnail on the screen, plus heartbeats. After clicking on a thumbnail, the URL changes in the browser, but nothing else happens. There are no client-side console errors. The server shows no errors either. Just a couple heartbeats per minute. I discovered something interesting in the network tab of the web console. The initial load usually shows around 74 assets. After clicking on a thumbnail and causing the issue, nothing will happen for a while. At this point I just leave it alone and watch. After about 10 minutes or so, I see the number of downloaded resources suddenly start to increase dramatically. They are all images named "320," with unique URLs. About 20 new resources stream in per second, and it will continue for thousands if I leave it. The other Safari windows become unresponsive at this point. Still no server-side log errors or client-side errors reported. Just normal heartbeats. I can even open a different browser, log in, and load the gallery. But if I click on a thumbnail in the other browser (firefox in this case), the same issue occurs. One thing I've noticed in the server logs is that there are always two GET messages that are displayed just as the flood begins. It's never the same two images. But it's always exactly two entries. The heartbeats will continue, but my web browser will become unresponsive at this point and the flood of resources in the network tab of the web console will begin. 9/27/2025, 8:02:23 PM[DEBUG] HEAD /heartbeat 200 2ms |
Beta Was this translation helpful? Give feedback.
-
|
This problem may be related to sort order. I've noticed that the exact same issue can occur when I change the sort order. Date always works, but if I change the sort order to random, I will get exactly the same error that I already described (ten minute delay and then a flood of network assets, along with two random thumbnail loads in the server logs) without clicking any thumbnails. I prefer a randomized asset order, so I've been running this with ungrouped, random set in the settings since I started. It didn't occur to me to try to change the sort order until just now. |
Beta Was this translation helpful? Give feedback.
-
|
My guess that you have a LOT (1000+) of photos in one folder and the app
just starts loading all of them at once.
I also noticed that sometimes scroll bar detection does not work properly
and the app just starts loading all the photos.
Can you confirm this full load? Maybe try another browser to see if it
works there?
Can you reproduce on the demo app?
I have ~80k photos in my library, so 120k should not be a problem.
…On Sun, 28 Sept 2025 at 04:44, Mark Poncelet ***@***.***> wrote:
This problem may be related to sort order. I've noticed that the exact
same issue can occur when I change the sort order. Date always works, but
if I change the sort order to random, I will get exactly the same error
that I already described (ten minute delay and then a flood of network
assets, along with two random thumbnail loads in the server logs) without
clicking any thumbnails.
I prefer a randomized asset order, so I've been running this with
ungrouped, random set in the settings since I started. It didn't occur to
me to try to change the sort order until just now.
—
Reply to this email directly, view it on GitHub
<#1043 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZKA5U4GFS36ZYJQHRX7ZT3U5DSJAVCNFSM6AAAAACHMCBBHOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJTGE4TINA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I made a commit, hopefully that helps |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I would love some help, as I've been working on this now for weeks and just can't figure out what's going on.
I have a big 100,000+ library. After a fresh install of 2.0.0 on the latest tag, all the initial ingest jobs work great. (I usually skip video transcoding, though.) Things work perfectly for a bit. Then I will come back later and click on a thumbnail only to see the URL change but nothing appear on the screen. Scrolling no longer loads new thumbnails in the gallery. If I close the browser and then come back, I can scroll through as many thumbnails as I want, but clicking on any of them causes the same problem. This is true in Safari and Firefox.
I'm not 100% sure, but I think the problem may start happening after I ungroup the thumbnails. I remember doing that as the last thing before the problem most recently happened.
The thing that gets me is that 1.9.5 works great with the same library.
This is a vanilla install straight from the latest tag with no settings changed from stock. I didn't install nginx, either. I'm stumped.
My environment is a debian VM in Proxmox, with images on a local drive. 2 cores, 8 GiB RAM. This VM is a clone of the one the 1.9.5 instance is running on, and they're accessing the same directory for image content. (Different pigallery2 directories, of course.)
Any ideas what I should do?
Beta Was this translation helpful? Give feedback.
All reactions