More > JRiver Media Center 27 for Windows
auto import high CPU usage, CSearchFilesHelper::GetResults: Search ?
mkolmar:
Same type of searches, album by album, logged again with high CPU usage. This time I turned off media network in MC, and high CPU usage stopped. Is there some connection between file import (which checks for files already in library), and media network, and CSearchFilesHelper::GetResults: Search?
I'm not aware of a way that Plex server would be able to try to index MC. I turned off MC as a media server for BubbleUPnP server, though I don't think it does any indexing. I've not been using JRemote (not installed) or BubbleUPnP client or Plex during this time. I need to know what type of activity is associated with CSearchFilesHelper::GetResults: Search, if that is something that an external tool can even cause to happen.
mkolmar:
Has this issue been addressed in MC28? I am not certain how often this is still happening, but it is. This morning I found MC27 highly unusually slow. CPU was maxed. Same type of searches as described appear repeatedly in the log. At times in the past, I know this activity yields to A/V playback, with no obvious slowdown.
Recently I bought JRemote2 again. Playing back through JRemote2 / BubbleUPnP DLNA to Chromecast audio is the only recent difference. MC is always running, and that playback was the last thing I did with MC.
Let's stipulate that the PC running MC27 is no powerhouse, capable of playing basic HD and not much more.
I have had to restart MC and/or affirmatively reconnect to the server a couple times to get JRemote2 to display results from the server. But I suspect JRemote2 simply was not connected, maybe hadn't timed out yet and did not give an error.
mkolmar:
Logs attached. Both logs show otherwise idle time -- no playback, no manual import, search, or anything.
First log is normal. TV (.105) presumably trying to detect media servers, but TV is not being used to browse or play.
Previous log shows MC eating its own tail? The .102 address is the PC that runs MC. It's not clear to me how to interpret the logging. What could produce these searches? Does it appear to be MC's requests to itself, or something hitting the media server?
MC was bogged down so badly just prior to this logging that it could not play back audio without stuttering. Restaring MC cleared the problem for now.
mkolmar:
Blocked smart TV in Windows Firewall from connecting to the PC that runs MC a few days ago. I have not seen MC with high, sustained CPU usage since. Let's see how it goes.
I assume the searches would have to use DLNA server, which the TV can do. The TV has not been used to play music or connect with MC or other media server, except as a test, so searches by the TV would be pointless and unwelcome.
MC log could be clearer about what activity is associated with requests from which host. It would also be handy to block IP addresses in the Interfaces to Ingore setting.
Navigation
[0] Message Index
[*] Previous page
Go to full version