1. NodeBox 1
    1. Homepage
    2. NodeBox 3Node-based app for generative design and data visualization
    3. NodeBox OpenGLHardware-accelerated cross-platform graphics library
    4. NodeBox 1Generate 2D visuals using Python code (Mac OS X only)
  2. Gallery
  3. Documentation
  4. Forum
  5. Blog

The cause of NodeBox startup crashes: input managers

Posted by Frederik on Jan 17, 2007

Some people have experienced crashes when trying to start up NodeBox. These are frequently caused by input managers they have installed. Input managers override code in applications like Safari or iChat to implement specific functionality. However, faulty compiler flags can cause them to crash the host application.

The workaround is to disable the offending input managers from either the /Library/InputManagers folder or your /Users/yourusername/Library/InputManagers folder.

The name of the offending input manager is clearly noted in the NodeBox crash log. As an example, here is a crash log caused by CaminoSession:

Thread 0 Crashed:
0           0x000091cc objc_msgSend + 0
1   eu.willmore.CaminoSession   0x149d5dd0 +[CaminoSession load] + 76 (CaminoSession.m:101)
2   libobjc.A.dylib             0x90a40548 call_class_loads + 164


Developers can make sure their of input managers works with NodeBox by setting the correct compiler flags. For more information, look here: http://article.gmane.org/gmane.comp.python.pyobjc.devel/4281

 


Posted by Ben on Jan 29, 2007

In the case of CaminoSession, a better solution is to upgrade to version 0.86 (http://willmore.eu/plugins/caminosession.html) in which this problem has been fixed.