C-Command Software Forum

Eaglefiler crash on startup

Not sure why this suddenly popped up, but here’s the console log. Thanks for any info to help me get up and running again.

01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] Traceback (most recent call last):
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] File “/Applications/EagleFiler.app/Contents/Resources/boot.py”, line 31, in <module>
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] _run(‘main.py’)
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] File “/Applications/EagleFiler.app/Contents/Resources/boot.py”, line 28, in _run
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] execfile(path, globals(), globals())
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] File “/Applications/EagleFiler.app/Contents/Resources/main.py”, line 34, in <module>
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] from wash import appcontroller
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] File “wash/appcontroller.pyc”, line 11, in <module>
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] File “wash/capture.pyc”, line 18, in <module>
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] File “wash/jobs.pyc”, line 11, in <module>
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] File “wash/records.pyc”, line 28, in <module>
01.09.10 10:29:08 [0x0-0x1ea1ea].com.c-command.EagleFiler[16154] objc.error: MJTException - SetMaximumFiles(1) at NSProcessInfo+MJT.m:68 +mjtSetMaximumOpenFilesCount:
01.09.10 10:29:08 EagleFiler[16154] EagleFiler Error
01.09.10 10:29:08 EagleFiler[16154] EagleFiler Error
EagleFiler encountered an unexpected error:

error: MJTException - SetMaximumFiles(1) at NSProcessInfo+MJT.m:68 +mjtSetMaximumOpenFilesCount:

This is actually an error, not a crash (hence no crash reporter). Please try restarting your Mac.

Sorry for the imprecision. True, it was not a crash per se, although EF quit immediately (after I dismissed the dialog), so it was crashesque in my mind.

Restarting fixed the issue. Can you give me an idea of what I did to upset EF so much?

Thank you
Jeremy

It’s probably nothing that you did, specifically. It just looks like some of the OS’s internal bookkeeping tables were either full or corrupted, and restarting cleaned them out.