@ChuckPa I think that could be a different issue. I have the same issue on WebOS where I can’t display photos and am willing to help contribute to get it fixed. They work fine on my Samsung TV (Tizen OS) and everywhere else.
Thanks for pinging me.
Discussed this in Engineering meeting today.
Current discussion is inconclusive.
They couldn’t reproduce it in the meeting and the video we had of it (capture) had been removed by the user.
I did get a much better understanding of the interaction between the clients and PMS.
Anything anyone can do to catch this in the act , with logs and video (
) would be ideal!
I will do whatever it takes to get this resolved.
@ChuckPa I was referring the issue @ant158 posted about that was moved here. I think it is a different issue specific to WebOS Plex client.
I posted the issue here (and forgot that I posted that). @ant158 originally posted it here, but it was moved to this discussion. I’m not sure they are related to this issue.
I can supply logs, but want to make sure it is in the right place.
Is there anyone here? does plex company read these pages? As I said, Plex is a paid product, it would be nice if you fixed the bugs before adding new features that you need to make new money, but you already took our money so what do you think about fixing this photo thing?
I presented the Photos issue today in our meeting.
I am aware the issue includes LG WebOS.
It also includes Plex/web and Nvidia Shield Pro. (I personally have reproduced this)
This is why I’m asking for any and all input so I can present it to Engineering.
The more info we can gather will help them know where to look.
Also getting this issue; as well, it happens when viewing content in the “Library” tab of Photos. Seems to be most common when there are multiple nested folders with lots of files in them; unsure. Clicking through 2~ nested folders does it generally. I have a feeling it might be some unusual file type or some outlier of that sort. Similar with everyone else, I don’t get this when viewing content in the timeline.
@ChuckPa Instinct tells me it has something to do with improper cleanup of some metadata collection when nested folders you don’t click into are unmounted in the DOM by clicking onto other folders.
Thanks for the Update, Chuck!
This is great! Thank you.
Engineering was considering Web but the LG WebOS and Shield’s involvement somewhat contradicts that.
This shines a bit of light on what’s happening. Thank you!
@ChuckPa I shared the video with streamable, the link expired after 2 days.
Here is a link to a proton share, you can download it from there if you want:
Btw, issue still exists after updating to 1.41.1.9057
1 Like
Thanks for the image again. NOW, I have it (with your name on it! lol)
The issue of course still exists 
Engineering hasnt had time to look at the problem and start work.
LOL
poke poke
FWIW, On Win11 (Firefox) I experience the problem if I click in the “general” tile area, but NOT if I click in the circle-arrow, where it then cycles through the pictures.
Server vers: 1.41.1.9057 (Win11 based).
I also do not experience the problem in any form (general grid or circle-arrow) using the Shield Pro as a client (same server).
Hi @ChuckPa, Hope to shine more light in to this. Looking at it again, I believe the failure everyone is encountering is due to an infection chain; more due to the warning right before the error in the console. I think this is the root defect; but more info the better!:
Here should be the right reproduction:
This error seems to only occur if when you open two nested folders sequentially in the UI:
- Fresh page; open the photos tab (Say Root Photos Directory: /mnt/images)
- Clicking on a folder in the library tab, e.g. “pets”
- Clicking on a nested folder inside /mnt/images/pets e.g. “Dogs” <— Error occurs here
This will continue happening for all nested folders beyond this, even if you refresh the page. (e.g. clicking on a folder “pets” after refreshing the page on “dogs”: /mnt/images/pets/dogs/puppies). This might be a possible recursion error?
If you have already loaded all the photos inside the nested folder you click into (e.g. refreshed the page in the folder, navigated back to the root photos directory, and clicked through), this issue will not occur. I presume this is because the metadata is no longer undefined. I was wrong in my previous message, I don’t think this has anything to do with unmounting, I think this has something to do with a photo entity being rendered without metadata getting set yet; or something like that. Maybe something to do with metadata state being “reset” when you navigate to a nested folder, then undefined, then set again. But its confusing why it would happen specifically after the second folder… Hard to grok or give a professional suggestion with no knowledge of the codebase, but this is the best amount of info I can give.
1 Like
Thank you!
That supports initial discussion we had.
This is a “smoking gun” of what’s happening.
Engineering initially thought this type error might be at the root.
I’ve added the screenshot error message to the issue
I don’t have visibility into the schedule but the engineer has been assigned to work on it.
( Efforts of the weekend got us the information we needed )
Yes, it indeed looks like the same “not defined before use” condition.
There is a good repro so far and Engineering has assigned an engineer
Still no fix for the photo problem?
1 Like
I have nothing to report at this time (no progress notes so far)
It’s assigned to the engineer and a release cycle.
this is ridiculous, any open source software would have solved such a serious problem in 24/48 hours
1 Like
