› ›

Repetier-Host Crashes Immediately after Slicing

HowdyHowdy
in Linux
Hello!  Thanks for reading through this.
I have downloaded and installed repetier-host.  When you open it for the first time, there's an .amf file of a tablet pc stand already.  This file has no problem slicing and printing.
However, when I try to slice any .stl file I have loaded, the bar moves across the screen and then the entire application disappears.  I get no error message and no dialog box.  Mind you, I'm not even sure it's the file type that's the problem.  There may be some other thing about the preloaded file that makes it work every time while things I load cause a crash.

Has anyone else had this problem?  

Thank you!

Comments

  • HowdyHowdy
    Hello!  Thanks for reading through this.
    I have downloaded and installed repetier-host.  When you open it for the first time, there's an .amf file of a tablet pc stand already.  This file has no problem slicing and printing.
    However, when I try to slice any .stl file I have loaded, the bar moves across the screen and then the entire application disappears.  I get no error message and no dialog box.  Mind you, I'm not even sure it's the file type that's the problem.  There may be some other thing about the preloaded file that makes it work every time while things I load cause a crash.

    Has anyone else had this problem?  

    Thank you!



    Some things that might also be helpful:
    1) I'm running Arch Linux.
    2) I've tried reinstalling several times, but the problem persists.
    3) I've tried installing the CuraEngine separately - and also the git version, but the build seems to unspool and result in never ending text, rather than the organized and annotated build process that results from simply installing repetier-host.
    4) Attempts to install Slic3r separately as an alternative to Cura have resulted in similar never ending text gobbledygook.
    5) I tried installing straight from the tarball, but the original crash problem persists there, too.

    Thank you!
  • RepetierRepetier
    Start from a terminal window, then you shoudl see a crash reason. If you use the desktop button no messages will be visible.

    Sounds like when slicer is finished the reading causes the crash. Can you read the sliced gcode after restarting the host? SHould be in host working directory.
  • HowdyHowdy
    OK, so when I type "repetierHost," I get this:

    [matt@mattsarchprime ~]$ repetierHost
    [matt@mattsarchprime ~]$ libpng warning: iCCP: known incorrect sRGB profile
    libpng warning: iCCP: known incorrect sRGB profile
    libpng warning: iCCP: cHRM chunk does not match sRGB

    . . . and those last two lines repeat roughly 40 times before it ends with:

    "Rebuild object False"

    This doesn't seem to prevent the launch, but there is clearly something a little off.
    After that, I click on the repetier window, load an .stl, and click the awesome, giant "slice with curaengine" button.  The bar moves across the screen, the window terminates, and the terminal then produces this (I apologize for the length):

    Unhandled Exception:
    System.ObjectDisposedException: Cannot access a disposed object.
    Object name: 'Stream has been closed'.
      at System.IO.FileStream.BeginRead (System.Byte[] array, Int32 offset, Int32 numBytes, System.AsyncCallback userCallback, System.Object stateObject) <0x7fecae53f800 + 0x00238> in <filename unknown>:0 
      at System.Diagnostics.AsyncStreamReader.ReadBuffer (IAsyncResult ar) <0x41623920 + 0x00425> in <filename unknown>:0 
      at System.IO.Stream+ReadWriteTask.InvokeAsyncCallback (System.Object completedTask) <0x7fecae39e330 + 0x00058> in <filename unknown>:0 
      at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x7fecae48bfc0 + 0x001c6> in <filename unknown>:0 
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x7fecae48bf90 + 0x00020> in <filename unknown>:0 
      at System.IO.Stream+ReadWriteTask.System.Threading.Tasks.ITaskCompletionAction.Invoke (System.Threading.Tasks.Task completingTask) <0x7fecae39e3b0 + 0x000f9> in <filename unknown>:0 
      at System.Threading.Tasks.Task.FinishContinuations () <0x7fecae47ab20 + 0x00214> in <filename unknown>:0 
      at System.Threading.Tasks.Task.FinishStageThree () <0x7fecae478f30 + 0x00068> in <filename unknown>:0 
      at System.Threading.Tasks.Task.FinishStageTwo () <0x7fecae478df0 + 0x00117> in <filename unknown>:0 
      at System.Threading.Tasks.Task.Finish (Boolean bUserDelegateExecuted) <0x7fecae478c50 + 0x0008d> in <filename unknown>:0 
      at System.Threading.Tasks.Task.ExecuteWithThreadLocal (System.Threading.Tasks.Task& currentTaskSlot) <0x7fecae479980 + 0x00135> in <filename unknown>:0 
      at System.Threading.Tasks.Task.ExecuteEntry (Boolean bPreventDoubleExecution) <0x7fecae479820 + 0x000f3> in <filename unknown>:0 
      at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () <0x7fecae4797a0 + 0x0000e> in <filename unknown>:0 
      at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x7fecae4909b0 + 0x001d6> in <filename unknown>:0 
      at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x7fecae4922b0 + 0x00008> in <filename unknown>:0 

    It doesn't end with a command prompt, either - which makes it feel like there's something still going on in there, even if the repetier host window is no longer visible.


    I tracked down the gcode (I think) in a file called /home/Prime/.local/share/RepetierHost/composition.gcode.  I deleted its contents and started the process over, in case the file was duplicating.  

    A default End Code is glued on the end of the file.  Interestingly, it's not the one that I clumsily pulled from a blog about using repetier with a da Vinci.  Here're the last 35ish lines:


    TYPE:WALL-OUTER
    G1 F540 X96.373 Y93.521 E1579.97486
    G1 X96.072 Y91.642 E1580.03816
    G1 X96.208 Y91.561 E1580.04342
    G1 X96.564 Y91.997 E1580.06214
    ;LAYER:529
    G0 F9000 X96.417 Y92.006 Z106.100
    ;TYPE:WALL-OUTER
    G1 F540 X96.318 Y92.794 E1580.08856
    G1 X96.151 Y91.748 E1580.12379
    G1 X96.188 Y91.726 E1580.12522
    G1 X96.417 Y92.006 E1580.13725
    ;LAYER:530
    G0 F9000 X96.269 Y92.014 Z106.300
    ;TYPE:WALL-OUTER
    G1 F540 X96.263 Y92.066 E1580.13899
    G1 X96.251 Y91.992 E1580.14149
    G1 X96.269 Y92.014 E1580.14243
    ;LAYER:531
    M106 S127
    ;LAYER:532
    M107
    G1 F2400 E1576.14243
    G0 F9000 X96.269 Y92.014 Z111.615
    ; Default end code
    ;G1 X0 Y0 Z130 ; Get extruder out of way. Uncomment to use!
    M107 ; Turn off fan
    ; Disable all extruder
    G91 ; Relative positioning
    T0
    G1 E-1 ; Reduce filament pressure
    M104 T0 S0
    G90 ; Absolute positioning
    G92 E0 ; Reset extruder position
    M140 S0 ; Disable heated bed
    M84 ; Turn steppers off

    Thank you again for all your help with this!
  • RepetierRepetier
    Slicer always stores result in /home/Prime/.local/share/RepetierHost/composition.gcode and then host reads it back, so that part seems to work except reading.

    The stacktrace only shows internal function no function from host it self, so it is unclear what read failed due to disposed object. Was it the complete backlog or did you only copy first part of it?

    The garbage at start is normal and can be ignore. Importnant is all that follows
    Unhandled Exception:
    System.ObjectDisposedException: Cannot access a disposed object.
    Object name: 'Stream has been closed'.

    will test it on my linux again.
  • HowdyHowdy
    That was the complete response on the terminal.

    Also, sometimes when I install repetier-host, the tablet .amf is not there when I open it. After I load an .stl, I can slice it without the program quitting - but only the first time. After that, files repetier will not read the file curaengine created, and the same problem picks up again.
  • RepetierRepetier
    Ok, tried it on ubuntu 14.04LTS with mono 3.2.8 and it worked multiple times even with bundled curaengine.

    Since I see no reference to host in the traceback I assume it is a mono internal part that causes the read error on a closed file. Could e.g. be the registry that is emulated by mono using a directory structure .mono/.... in your home directory. After loading the history is updated, so we in deed change registry. Would also maybe explain why it works first time. For more insight you might try calling it like
    strace repetierHost
    which writes lots of informations to console like files opened or closed and system calls.
  • HowdyHowdy
    It seems to be working now (and I'm really looking forward to calibrating and seeing what the printer can do).

    I think Mono 4.6.1.3-1 is the one I'm on. It sounds like it wasn't the problem, though. It may have been another library, somewhere. I think I've done more updates just this week than in any month since I first installed the OS.

    Either way, I really appreciate your help with it - thank you!
Sign In or Register to comment.