Repetier Host 2.01 crashes after server shutdown

Icarus

More often than not when I do a 'server shutdown' from the menu Reptier Host will ask if I'm sure, after selecting Yes, will disconnect and shutdown the server and then it will freeze RH for a moment before I get an error message: "RepetierHost has stopped working. A problem caused the program to stop etc etc". Then the program exits.
I'm running RH V2.01 on Win 10 and the server on a Raspberry Pi3 V0.85.0

Repetier

You can not shutdown the server from Repetier-Host if it is not running on the same machine (Stop local server). So this means you are shutting down the server on your windows machine and not the one on the Raspberry!

Or do you mean shutdown in the raspberry frontend while connected to host?

Icarus

I am not trying to stop the local server (it's not running anyway). Repetier Host is connected to Repetier Server in the printer settings using the Pi's IP address / Port 3344 and the API key. So, from Repetier Host, when I go to Printer > Shutdown Server, after answering Yes to 'Really shutdown server' it crashes Repetier Host.

Repetier

Ok, I understand. So the unexpected disconnect seems to cause the crash. Unfortunately I can not reproduce it. I get a message that the IP is not available any more, connection is closed and I can continue. Does the error window contain any more details? If not windows events should show more infos on the crash. Will keep an eye on it and try some more times, but it might also depend on some other conditions I do not meet.

Icarus

Here's the Windows event error logs and screenshot....

Log Name: Application

Source: .NET Runtime

Date: 21/07/2017 20:46:18

Event ID: 1026

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: Paul-Desktop

Description:

Application: RepetierHost.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.AccessViolationException

at OpenTK.Graphics.OpenGL.GL.DeleteBuffers(Int32, Int32[])

at RepetierHost.model.GCodePath.UnbufferVBOs()

at RepetierHost.model.GCodePath.Free()

at RepetierHost.model.GCodeVisual.Clear()

at RepetierHost.Main.ClearPrintPreview()

at RepetierServerConnector.ServerConnector.Connect(Boolean)

at RepetierServerConnector.ServerConnector.RunPeriodicalTasks()

at RepetierHost.model.PrinterConnection.handleTimer(System.Object, System.EventArgs)

at System.Timers.Timer.MyTimerCallback(System.Object)

at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.TimerQueueTimer.CallCallback()

at System.Threading.TimerQueueTimer.Fire()

at System.Threading.TimerQueue.FireNextTimers()

Event Xml:

<Channel>Application</Channel>

<Computer>Paul-Desktop</Computer>

</System>

<Data>Application: RepetierHost.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.AccessViolationException

at OpenTK.Graphics.OpenGL.GL.DeleteBuffers(Int32, Int32[])

at RepetierHost.model.GCodePath.UnbufferVBOs()

at RepetierHost.model.GCodePath.Free()

at RepetierHost.model.GCodeVisual.Clear()

at RepetierHost.Main.ClearPrintPreview()

at RepetierServerConnector.ServerConnector.Connect(Boolean)

at RepetierServerConnector.ServerConnector.RunPeriodicalTasks()

at RepetierHost.model.PrinterConnection.handleTimer(System.Object, System.EventArgs)

at System.Timers.Timer.MyTimerCallback(System.Object)

at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.TimerQueueTimer.CallCallback()

at System.Threading.TimerQueueTimer.Fire()

at System.Threading.TimerQueue.FireNextTimers()

</Data>

</EventData>

</Event>

Log Name: Application

Source: Application Error

Date: 21/07/2017 20:46:19

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Paul-Desktop

Description:

Faulting application name: RepetierHost.exe, version: 1.0.0.0, time stamp: 0x5910a761

Faulting module name: ig75icd64.dll, version: 20.19.15.4531, time stamp: 0x57ed2465

Exception code: 0xc0000005

Fault offset: 0x0000000000743a2e

Faulting process ID: 0x1834

Faulting application start time: 0x01d30248f0475886

Faulting application path: C:\Program Files\Repetier-Host\RepetierHost.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ig75icd64.dll

Report ID: 8be252e3-d6ec-40fe-a525-bcb29bc461e5

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>Paul-Desktop</Computer>

</System>

<Data>RepetierHost.exe</Data>

<Data>C:\Program Files\Repetier-Host\RepetierHost.exe</Data>

<Data>C:\WINDOWS\SYSTEM32\ig75icd64.dll</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

Repetier

Ok, I see it happens in freeing OpenGL resources. I also see that this path may be executed outside main thread which could be a problem. So for next release 2.0.2 I have now ensured this will run in main thread instead.

If it persists in 2.0.2 let me know so I can dig deeper.

Icarus

Will do - when is 2.0.2 going to be released? Keep up the good work!

Repetier

Very soon. more or less finished and only running some tests to verify it works as expected.

Icarus

There's still an issue in V2.0.5. After server shutdown and confirmation, RH just sits there with a 'Not Responding' message. Event Viewer doesn't log anything until I force close the program and just shows an application hang message.

Repetier

Did you wait long enough? It might take a while until host detects the connection is down and it will try even to reconnect. So you get here some blocking until network times out and returns failed connect. Had this at least with wrong ips and it can take a bit until it responds again.

Icarus

I waited about 4 to 5 minutes before I closed the program....