Connection to Emacs lost
Created by: reiniervandijk
Occasionally, the connection of the lisp console to Emacs goes lost. Hard to replicate. For me it happened during compilation of a file and having Tasty open with reasonably sized X3D model.
dispatch-event: (:return #<multiprocessing:process worker @ #x29772fc2> (:ok "t") 1504)
encode-message
decode-message
dispatch-event: (:emacs-rex (swank:autodoc (quote ()) <User Code> swank::%cursor-marker%))) :print-right-margin 155) ":move" t 1505)
close-connection: Attempt to start thread worker gave OS error code 0xc ...
;; Event history end.
;; Backtrace:
;; Connection to Emacs lost. [
;; condition: Attempt to start thread worker gave OS error code 0xc
;; type: simple-error
;; style: :spawn]
Imported comments:
By genworks on 2013-02-18 19:41:53 UTC
We are going to upgrade to the latest swank/slime in the next release (by end of this month, including full Enterprise 1582), and see if this continues to be an issue.
This Issue will remain open until the problem is clearly resolved.
In the meantime be aware that the Franz ELI is always available as an alternative to Slime - with packaged Gendl releases you can start ELI with
M-x gdl
instead of
M-x gendl