Nice, I'm going through the logs now. Hope you're a bit less sore today! I'm off to do Brazilian jiu jitsu after this so I'm prepared to be sore too
Here are my notes from the logs:
At 2021-12-27 08:50:59.066 we get a browse request for the root folder, to which we respond, including the Media Library (ID 28) and Pictures (ID 56) directories:
Code: Select all
<container childCount="3" id="28" parentID="0" restricted="1">
<dc:title>Media Library</dc:title>
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" protocolInfo="http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_SM;DLNA.ORG_FLAGS=00900000000000000000000000000000">http://192.168.50.153:5001/get/28/thumbnail0000JPEG_SM_Media+Library.jpg</res>
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" protocolInfo="http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_TN;DLNA.ORG_FLAGS=00900000000000000000000000000000">http://192.168.50.153:5001/get/28/thumbnail0000JPEG_TN_Media+Library.jpg</res>
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" protocolInfo="http-get:*:image/png:DLNA.ORG_PN=PNG_LRG;DLNA.ORG_FLAGS=00900000000000000000000000000000">http://192.168.50.153:5001/get/28/thumbnail0000PNG_LRG_Media+Library.png</res>
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" protocolInfo="http-get:*:image/png:DLNA.ORG_PN=PNG_TN;DLNA.ORG_FLAGS=00900000000000000000000000000000">http://192.168.50.153:5001/get/28/thumbnail0000PNG_TN_Media+Library.png</res>
<upnp:albumArtURI xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" dlna:profileID="JPEG_SM">http://192.168.50.153:5001/get/28/thumbnail0000JPEG_SM_Media+Library.jpg</upnp:albumArtURI>
<upnp:albumArtURI xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" dlna:profileID="JPEG_TN">http://192.168.50.153:5001/get/28/thumbnail0000JPEG_TN_Media+Library.jpg</upnp:albumArtURI>
<upnp:albumArtURI xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" dlna:profileID="PNG_LRG">http://192.168.50.153:5001/get/28/thumbnail0000PNG_LRG_Media+Library.png</upnp:albumArtURI>
<upnp:albumArtURI xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" dlna:profileID="PNG_TN">http://192.168.50.153:5001/get/28/thumbnail0000PNG_TN_Media+Library.png</upnp:albumArtURI>
<upnp:class>object.container.storageFolder</upnp:class>
</container>
<container childCount="1" id="56" parentID="0" restricted="1">
<dc:title>Pictures</dc:title>
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" protocolInfo="http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_SM;DLNA.ORG_FLAGS=00900000000000000000000000000000">http://192.168.50.153:5001/get/56/thumbnail0000JPEG_SM_Pictures.jpg</res>
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" protocolInfo="http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_TN;DLNA.ORG_FLAGS=00900000000000000000000000000000">http://192.168.50.153:5001/get/56/thumbnail0000JPEG_TN_Pictures.jpg</res>
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" protocolInfo="http-get:*:image/png:DLNA.ORG_PN=PNG_LRG;DLNA.ORG_FLAGS=00900000000000000000000000000000">http://192.168.50.153:5001/get/56/thumbnail0000PNG_LRG_Pictures.png</res>
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" protocolInfo="http-get:*:image/png:DLNA.ORG_PN=PNG_TN;DLNA.ORG_FLAGS=00900000000000000000000000000000">http://192.168.50.153:5001/get/56/thumbnail0000PNG_TN_Pictures.png</res>
<upnp:albumArtURI xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" dlna:profileID="JPEG_SM">http://192.168.50.153:5001/get/56/thumbnail0000JPEG_SM_Pictures.jpg</upnp:albumArtURI>
<upnp:albumArtURI xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" dlna:profileID="JPEG_TN">http://192.168.50.153:5001/get/56/thumbnail0000JPEG_TN_Pictures.jpg</upnp:albumArtURI>
<upnp:albumArtURI xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" dlna:profileID="PNG_LRG">http://192.168.50.153:5001/get/56/thumbnail0000PNG_LRG_Pictures.png</upnp:albumArtURI>
<upnp:albumArtURI xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" dlna:profileID="PNG_TN">http://192.168.50.153:5001/get/56/thumbnail0000PNG_TN_Pictures.png</upnp:albumArtURI>
<dc:date>2021-12-23T16:42:36</dc:date>
<upnp:class>object.container.storageFolder</upnp:class>
</container>
The problem happens here:
At 2021-12-27 08:51:01.801 we delete ID 56 from the global ID repo (a garbage collection event that happens)
At 2021-12-27 08:51:02.849 we get the next browse request for the children of Pictures, which doesn't exist anymore:
Code: Select all
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:Browse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1">
<ObjectID>56</ObjectID>
<BrowseFlag>BrowseDirectChildren</BrowseFlag>
<Filter>id,dc:title,dc:description,dc:date,upnp:longDescription,upnp:artist,upnp:album,upnp:albumArtURI,upnp:rating,upnp:scheduledStartTime,upnp:genre,res,res@duration,res@bitrate,res@size,res@protocolInfo,res@resolution,container@childCount,upnp:originalTrackNumber,res@pv:subtitleFileType,res@pv:subtitleFileUri</Filter>
<StartingIndex>0</StartingIndex>
<RequestedCount>10</RequestedCount>
<SortCriteria/>
</u:Browse>
</s:Body>
</s:Envelope>
To which we respond with an empty request because the ID doesn't exist anymore:
Code: Select all
DEBUG 2021-12-27 08:51:03.633 [HTTPv2 Request Worker 1] net.pms.dlna.GlobalIdRepo GlobalIdRepo: id not found: 56
TRACE 2021-12-27 08:51:03.633 [HTTPv2 Request Worker 1] net.pms.network.RequestV2 Empty response sent to Unknown renderer:
HEADER:
HTTP/1.1 204 No Content
Server: Windows_10-amd64-10.0, UPnP/1.0 DLNADOC/1.50, UMS/10.14.2-SNAPSHOT
Content-Length: 0
Unfortunately that's a tricky bug to fix because it's a symptom of a fix for a worse bug. Since you might be interested in an explanation, in the past, we did not have this bug because we held on to all the IDs, but that would lead to running out of memory if the server was on for a long time and/or with very large libraries. So the fix was to make IDs expire, but it was done in a simplistic way and so it can cause these problems. It's better than running out of memory, since the user can usually go out of the folder and enter it again as a workaround, which should give a fresh ID (if the renderer updates it)
At the time the fix was done, I didn't have the ability or understanding to do a better fix, but I might be able to do it now. I'll have a think about it and get back to you.
In the meantime here is your latest build which hopefully adds some polish to the SystemUpdateID fix from before, it would be good to know if it still works
https://www.universalmediaserver.com/up ... d48e83.exe