[further infos missing] MePo chrashed after ending a radio stream ... (1 Viewer)

[megahorst]

After stopping a DVB-C radio stream MePo chrashed.

Logs are added

 

[megahorst]

I had this issue again.
DVB-C radio was playing for several hours. After stopping MePo crashed.

I error.log I can see:

2013-01-27 18:02:00.354382 [ERROR][MPMain(1)]: MediaPortal stopped due to an exception Der Wert darf nicht NULL sein. mscorlib	bei System.Threading.Monitor.Enter(Object obj)
  bei MediaPortal.Player.BaseTSReaderPlayer.UpdateCurrentPosition()
  bei MediaPortal.Player.BaseTSReaderPlayer.get_CurrentPosition()
  bei MediaPortal.Player.g_Player.get_CurrentPosition()
  bei MediaPortalApp.OnProcess()
  bei MediaPortal.D3DApp.Application_Idle(Object sender, EventArgs e)
  bei System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
  bei System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
  bei System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
  bei System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
  bei System.Windows.Forms.Application.Run(Form mainForm)
  bei MediaPortalApp.Main(String[] args)

 

[Owlsroost]

It looks like MP is stopping play, closing down and cleaning up the graph - but then asking the graph for a duration update, which - not surprisingly - is generating an exception.....(since the graph no longer exists, as far as I can tell from the logs).

@Sebastiii - any thoughts ?

Tony

 

[Sebastiii]

Hi Tony,

Yep from log i see like you and in UpdateCurrentPosition() it should return like graph no longer exists.

protected void UpdateCurrentPosition()
	{
	  if (_mediaSeeking == null || _graphBuilder == null || Thread.CurrentThread.Name != "MPMain")
	  {
		return;
	  }

@megahorst does it happen after few minutes play too ?

 

[tourettes]

Hi Tony,

Yep from log i see like you and in UpdateCurrentPosition() it should return like graph no longer exists.

Should, but the code doesn't seem to do so - it could be some threading issue where other thread closes down the graph and then UpdateCurrentPosition() manages to access the free graph.

edit - based on the logs this is probably what happened:

2013-01-27 18:02:00.143370 [Debug][(3)]: Remove filter from graph: TsReader 0
2013-01-27 18:02:00.152370 [Debug][(3)]: TSReaderPlayer: Cleanup _graphBuilder

2013-01-27 18:02:00.286378 [Info.][MPMain(1)]: Exception ystem.ArgumentNullException: Der Wert darf nicht NULL sein.

Two different threads are poking around the same place.

It could be the WIFI remote thread that causes the wrong thread to do the graph cleanup.

2013-01-27 18:01:49.952787 [Debug][(3)]: [WIFI_REMOTE] Sending dialog close to clients

All events need to be processed in the main thread (as MP is not thread safe in many places).

 

[megahorst]

Hi Tony,

Yep from log i see like you and in UpdateCurrentPosition() it should return like graph no longer exists.

protected void UpdateCurrentPosition()
	{
	  if (_mediaSeeking == null || _graphBuilder == null || Thread.CurrentThread.Name != "MPMain")
	  {
		return;
	  }

@megahorst does it happen after few minutes play too ?

I have seen this only three or four times after closing long radio sessions.

I was not using WiFi remote at this time and there was no other client loged in with a WiFi remote client.

 

[megahorst]

Is there anything that I can do for further clarification?
Should I open a thread in the WiFi remote section?

 

[tourettes]

If you werent using wifi remote then it is quite weird. Log looks like wifi remote causes the directshow graph to be cleaned from the wifi remote's thread.

It would be good to investigate on wifi remote's side why &how such happens.

 

[DieBagger]

If you werent using wifi remote then it is quite weird. Log looks like wifi remote causes the directshow graph to be cleaned from the wifi remote's thread.

It would be good to investigate on wifi remote's side why &how such happens.

I'll take a look at it...

 

[DieBagger]

Is there anything that I can do for further clarification?
Should I open a thread in the WiFi remote section?

Could you try to reproduce this with WifiRemote DISABLED?