Forum rss-feed


Software: EigenD 2.0.74 Stable crashes under 10.9.4

Most Recent

written by: dhjdhj

You're absolutely right. Not exactly sure how a stale EigenD got there but all is fine


written by: dhjdhj

Thu, 19 Jun 2014 13:27:53 +0100 BST

I updated to 10.9.4 last night, by mistake, actually, I wasn't ready to do that.

Anyhow, EigenD crashes upon startup. Here's the crashed thread

Process: eigend [6624]
Path: /Applications/
Version: 2.0.74-stable
Code Type: X86 (Native)
Parent Process: launchd [252]
Responsible: eigend [6624]
User ID: 501

Date/Time: 2014-06-19 08:25:50.476 -0400
OS Version: Mac OS X 10.9.4 (13E16)
Report Version: 11
Anonymous UUID: 13A22ECC-1A10-E463-9338-0DE06813F2C1

Crashed Thread: 0 Juce Message Thread Dispatch queue:

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
abort() called
terminating with uncaught exception of type pic::error: Can't bind mcast socket: Address already in use from eigend-gpl/picross/pic_log.h:87 ()

Thread 0 Crashed:: Juce Message Thread Dispatch queue:
0 libsystem_kernel.dylib 0x92df7952 __pthread_kill + 10
1 libsystem_pthread.dylib 0x9190b167 pthread_kill + 101
2 libsystem_c.dylib 0x9661629c abort + 155
3 libc++abi.dylib 0x95c016c9 abort_message + 169
4 libc++abi.dylib 0x95c2247d default_terminate_handler() + 264
5 libc++abi.dylib 0x95c1fc30 std::__terminate(void (*)()) + 14
6 libc++abi.dylib 0x95c1f64b __cxa_throw + 116
7 libpic.dylib 0x0047f362 pic::maybe_abort(char const*, char const*, unsigned int) + 546
8 libpia.dylib 0x004c27da pic::hurl(pic::msg_t const&) + 490
9 libpia.dylib 0x0053b3aa (anonymous namespace)::recv_socket_t::recv_socket_t(unsigned int, unsigned long, bool) + 1002
10 libpia.dylib 0x0053bc28 (anonymous namespace)::interface_t::interface_t(pie_bkernel_t*, unsigned long, bool) + 72
11 libpia.dylib 0x0053cf91 pia::udpnet_t::udpnet_t(pic::nballocator_t*, bool) + 433
12 libpia.dylib 0x004db125 pia::scaffold_gui_t::scaffold_gui_t(pic::functor_t const&, pic::functor_t const&, pic::functor_t const&, pic::functor_t const&, bool, bool) + 325
13 libejuce.dylib 0x0089f9af ejuce::Application::impl_t::impl_t(ejuce::Application*, pic::functor_t const&, bool, bool) + 287
14 libejuce.dylib 0x0089fc8b ejuce::Application::initialise(juce::String const&, pic::functor_t const&, bool, bool) + 75
15 0x00011c79 EigenD::initialise(juce::String const&) + 1065
16 libjuce.dylib 0x00b3ba07 juce::JUCEApplication::initialiseApp(juce::String const&) + 487
17 libjuce.dylib 0x00b3f7fd juce::JUCEApplication::main(juce::String const&) + 109
18 libjuce.dylib 0x00b3fa1c juce::JUCEApplication::main(int, char const**) + 252
19 0x00002bf9 start + 53

written by: TheTechnobear

Thu, 19 Jun 2014 14:45:39 +0100 BST

sorry, I don't have access to 10.9.4
I would say given the stack trace its possibly a conflict on the port used by stage to communicate with eigenD.

have you tried to reboot, just in case in a process hanging onto the port?

once you have rebooted, if it still crashes, perhaps do a netstat to determine what ports are being listened on... see if 'stages port' has been grabbed by some other process. (you could use lsof to track this down)

written by: TheTechnobear

Thu, 19 Jun 2014 14:50:09 +0100 BST

gives the port used, by default 55555

(id think most likely its going to be a 'stale' eigend lurking around)

written by: geert

Thu, 19 Jun 2014 16:18:47 +0100 BST

This is most certainly a stale EigenD running, just reboot and try again.

written by: dhjdhj

Fri, 20 Jun 2014 23:20:26 +0100 BST

You're absolutely right. Not exactly sure how a stale EigenD got there but all is fine


Please log in to join the discussions