INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Still pb with MC Freeze  (Read 459 times)

PhDSM

  • Regular Member
  • World Citizen
  • ***
  • Posts: 191
Still pb with MC Freeze
« on: June 15, 2020, 01:26:54 pm »

Hello,
I'm back with my Freeze problem that I mentionned last year, , started with MC24 and  was never fixed (now we are at MC-26)

about several time a day MC freezes (no respond need to be aborted).
Its occurs in relation either with DLNA device  or when I access it from Android Gizmo (on LAN) after several hours on "no activity".
After been aborted and restarted, it works ok  until next day or next long non-usage.

I did further investigation but now I'm stuck. MC freeze about 10 time a day and I can't figure eactly why ?

I suspect DLNA-server <> DLMA rendererd communication. because it occurs only when music is played on Raspberry DNLA renderers.
In fact I know that I do too much volume adjustment it freeze.
Volume can be done via MC windows UI or Gizmo  or directly on renderer,  all these cases may generate freeze (sometime 5 time in a row, sometime once every x? volume changes

What I have already tried :
 - update drivers
 - adjusment of Windows Defender as mentionned in Taming Windows Defender on Windows 10 for JRiver Media Center,
 - Intensive Check of HDD, I even change it
 - move IP Renderer  from fixedIP to DHCP
 - Disable all podcast updates
 - change DNLA server config ( mp3, PCM16, PCM24)
 - implement a batch that saves JRiver log before killing it (so I have plenty of log files)
 
Attached : detail of my config  and a zip of log files saved after kill and before restarting

What can I do now? .  Is it a bug,  is it my config ? ...

Regards
Phil

Logged

PhDSM

  • Regular Member
  • World Citizen
  • ***
  • Posts: 191
Re: Still pb with MC Freeze
« Reply #1 on: June 18, 2020, 08:43:44 am »

Additional info,  i noticed that frequently the log end on :

0119000: 7212: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0119000: 7212: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.151: M-SEARCH: http://239.255.255.250:1900*
0119110: 7212: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (110 ms)
0119110: 15708: Sharing Plugins: CUDPSocketReader::Accept: Start
0119110: 15708: Sharing Plugins: CUDPSocketReader::Accept: Description: CListenerBase::CListenerBase [UDP]
0119110: 15708: Sharing Plugins: CUDPSocketReader::Accept: Finish (0 ms)
0119110: 8272: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0119110: 8272: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.151: M-SEARCH: http://239.255.255.250:1900*


it is like if the "Sharing Plugins: CHTTPListenerWorker::HandleReques" generate a "dead lock" (i.e process not reponding for ever)
Logged

PhDSM

  • Regular Member
  • World Citizen
  • ***
  • Posts: 191
Re: Still pb with MC Freeze
« Reply #2 on: August 24, 2020, 03:28:38 am »

Hi

I did more invesgating,  and it seems that it is linked with wifi quality signal,  when the raspberry running the DLNA renderer has low Wifi Signal, MC tend to freeze especially if I ask for volume change .
I move the RP nearer to the wifi AP then I get no freeze,  if I move away I get regular freezes, it seems linked with the way MC communicate with  the renderer
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: Still pb with MC Freeze
« Reply #3 on: August 24, 2020, 08:02:10 am »

That's just a network problem.  The signal is too weak to be reliable.
Logged
Pages: [1]   Go Up