INTERACT FORUM
More => Old Versions => JRiver Media Center 26 for Mac => Topic started by: curtisls87 on July 08, 2020, 12:05:23 am
-
I've only noticed this on my MBP, not on my iMac. For some reason, intermittently, the CPU usage goes up to over 200% in the Activity Monitor, when it is normally around 12%. I've attached a screen shot. I am running 26.0.94, although this happened on at least the previous version. I notice it because when it happens, the fan in the MBP kicks on. If I restart the application, it drops back to the 12% range. There doesn't seem to be any correlation with what I'm playing, as often I'm just streaming an AAC feed, or a FLAC feed. Even if I stop what's playing and play something else, it doesn't go away - I have to restart the application to go back to normal CPU usage.
The MBP is a mid-2012 Retina 2.6GHz i7 with 16 GB RAM running Catalina. The iMac that doesn't have a problem was new last year and is also running Catalina.
Any ideas would be appreciated.
-
ah yeah, syncing all your music with iCloud
-
Thank you for responding, but I don't think so. I have close to 10 TB of music files that are served from a FreeNAS server, and only a 50GB iCloud account.
-
Do MC's system report and check on the percentage of thumbnails built.
-
Here are the system reports from the MBP, the iMac 24 and the iMad 27. They all point to the same data store. The thumbnail builds are 9%, 42% and 12%, respectively. I don't have the CPU issue on either of the iMacs.
Any help is appreciated!
-
You could try a couple of things.
1) build missing thumbnails (set the threading to medium not high to avoid overheating your MBP).
2) Start logging in MC and see what it's doing during high CPU usage.
-
Looking at the logs, I'm seen a large number of time outs when building thumbnails. Not sure if that's the issue, but a cursory look at one of the iMacs doesn't show this. Here is an example.
370741185: 123145513033728: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
370741195: 123145513033728: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.69: GET: http://192.168.1.94:52100/AArl/13991468.jpg
370741195: 123145513033728: General: CThumbnailCacheInfo::CreateThumbnail: Start
370741195: 123145513033728: General: CThumbnailCacheInfo::CreateThumbnail: Filename: http://192.168.1.69:52199/MCWS/v1/File/GetImage?File=13991468&Type=Full
370741230: 123145513033728: General: CThumbnailCacheInfo::CreateThumbnail: Finish (35 ms)
370741236: 123145517326336: General: CAppleINetReader::Open: timed out waiting for bytes available
370741242: 123145517326336: Sharing Plugins: VHTTPMessage::Write: Wrote 3515 bytes
370741242: 123145517326336: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (20047 ms)
370741242: 123145517326336: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 602
-
Looking at the logs, I'm seen a large number of time outs when building thumbnails. Not sure if that's the issue, but a cursory look at one of the iMacs doesn't show this. Here is an example.
370741185: 123145513033728: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
370741195: 123145513033728: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.69: GET: http://192.168.1.94:52100/AArl/13991468.jpg
370741195: 123145513033728: General: CThumbnailCacheInfo::CreateThumbnail: Start
370741195: 123145513033728: General: CThumbnailCacheInfo::CreateThumbnail: Filename: http://192.168.1.69:52199/MCWS/v1/File/GetImage?File=13991468&Type=Full
370741230: 123145513033728: General: CThumbnailCacheInfo::CreateThumbnail: Finish (35 ms)
370741236: 123145517326336: General: CAppleINetReader::Open: timed out waiting for bytes available
370741242: 123145517326336: Sharing Plugins: VHTTPMessage::Write: Wrote 3515 bytes
370741242: 123145517326336: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (20047 ms)
370741242: 123145517326336: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 602
Interesting, this line:
370741195: 123145513033728: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.69: GET: http://192.168.1.94:52100/AArl/13991468.jpg
Sure makes it look like at least that one is being accessed via DLNA.
This one:
370741195: 123145513033728: General: CThumbnailCacheInfo::CreateThumbnail: Filename: http://192.168.1.69:52199/MCWS/v1/File/GetImage?File=13991468&Type=Full
Makes it look as if you are using library server.
Where is the media for the MBP stored?
-
The 192.168.1.69 address is the address of my primary JRiver Media Center, running on an iMac. I use the Connect To Remote Library function on the MBP to point to iMac's library so that all of the same music files are available on the MBP.
However, I store the media content on a FreeNAS server, at IP address 192.168.1.91. The iMac library points to the files on that.
-
So the client MC is using library server to grab the files from your MC library server machine to make thumbnails from the actual media stored on the NAS.
This really should be ok though there will be a fair amount of network traffic depending on how the album artwork is stored.
Just for testing, you can pull out one of those URL's from the log and put it into a browser on the client machine to see what happens.
http://192.168.1.69:52199/MCWS/v1/File/GetImage?File=13991468&Type=Full
Would be one example.
-
Finally got around to trying that. Here is what the browser returned.
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Response Status="Failure"/>
-
Finally got around to trying that. Here is what the browser returned.
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Response Status="Failure"/>
Interesting, it seems to be saying that the Library server machine can't pull the information from your NAS for that file.
Is the artwork stored on the NAS as well or the library server or in the file tags only??