Bug #1462

bag-play randomly crashes on macos

Added by J. Wienke almost 11 years ago. Updated almost 11 years ago.

Status:ClosedStart date:04/15/2013
Priority:NormalDue date:
Assignee:J. Moringen% Done:

0%

Category:-
Target version:Robotics Service Bus - rsb-0.9

Description

On mountain lion (10.8) at random times bag-play crashes with this error message:

fatal error encountered in SBCL pid 363(tid 58729472):
mach_port_allocate_name failed with return_code 5

Afterwards I am in LDB.

This might be related to previously letting the laptop sleep, but I am not sure about that.

I did not use the most recent builds of bag-play with the new lisp version.

History

#1 Updated by J. Moringen almost 11 years ago

This issue seems to have been fixed in version 1.0.47 of SBCL (release ~ 2012-08). Could you add the output of bag-play --version (which includes the SBCL version)?

#2 Updated by J. Wienke almost 11 years ago

My version is newer :/

languitar@miles:~/work$ bag-tools/master/bag-play --version
WARNING:
   Failed to load Spread library: Unable to load any of the alternatives:
   ("libspread-without-signal-blocking.dylib" "libspread.dylib" 
    "libspread.2.dylib" "libspread.2.0.dylib" "libspread.1.dylib").
   Spread functionalitywill not be available.
bag-tools/master/bag-play version 0.9.3-g13dcd47
SBCL version                      1.0.57
RSB version                       0.9.9-gc578974
RSBAG version                     0.9.16-g2bfafc1
RSBAG-TIDELOG version             0.9.16-g2bfafc1

#3 Updated by J. Moringen almost 11 years ago

Indeed. Could you still try the new executable?

#4 Updated by J. Wienke almost 11 years ago

After lunch ;)

#5 Updated by J. Moringen almost 11 years ago

  • Status changed from New to Feedback

Any observations with the new executable?

#6 Updated by J. Wienke almost 11 years ago

So far I didn't experience that error. To my mind we can resolve this issue and I will reopen it if this error appears again.

#7 Updated by J. Moringen almost 11 years ago

  • Status changed from Feedback to Closed

Reopen if necessary.

#8 Updated by J. Moringen almost 11 years ago

Turns out, there has been another fix for this issue in SBCL 1.0.58. So updating 1.0.57 -> 1.1.5 may have actually fixed the issue.

Also available in: Atom PDF