Eagle 6.3 crashing a lot

Version 6.4 seems to be better.  I haven't used it much yet, but I tried processing a CAM job and it didn't crash.  This would always crash in v6.3 on my Mac.

I just ran a CAM job 2 times and it Eagle 6.3 crashed after both.  I'm on Mac with OSX 10.7.5.  I haven't upgraded to 6.4 yet.  Anyone know if the crashing problem was fixed in that version?

I followed your instructions on setting the file permissions and Eagle crashed on me again.  I tried to close Eagle without saving some changes I made - I didn't want them saved - and it just crashed then gave me a report. 

Previously I was having most of my problems after processing CAM files, but I haven't done that in a while, so I don't know if that's any better or not.

This probably isn't a whole lot of help, but it may provide a tidbit -

somewhere some time ago, I remember people having problems on Mac's with

some program when running Parallels or one of those that had to do with the

"save as" - everything else was working if I remember correctly, but

something about "save as" was an issue and supposedly the "fix" was going

to be in the next release of Parallels or whichever one it was.  Sorry I

don't remember any more than that about it, but it did involve "save as"

causing things to break.

mikey

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Isolated the problem to a specific set of actions:

if I choose "save as" and then click on the drop down menu to choose recent folders in the dialog that pops up it crashes instantly. If instead browse by clicking folders at the side I can get to where I need and save.

Tried your change ownership method but I get the following error:

<username> is not in the sudoers file.  This incident will be reported.

I just migrated my copy of 6.3 from my older macbook pro (running snow leopard) to a brand new MBP running the latest version of Lion.

Everytime I open an old schematic and then go to save it as a new file name it crashes.

Excerpt of the crash report:

Parent Process:  launchd [2079]

Report Version:  10

Per-App Interval Since Last Report:  77 sec

Per-App Crashes Since Last Report:   1

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000000005d08c4a3

VM Regions Near 0x5d08c4a3:

-->

Application Specific Information:

objc_msgSend() selector name: autorelease

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

On 12/4/2012 6:56 PM, Richard Goodrich wrote:

I bought it a year ago and am just now using it and it crashes every time I turn around!

 

Hi Guys,

We're currently chasing down some MAC OS bugs. So far no one has been

able to provide a reliable procedure to recreate a crash. I've attempted

to recreate all reports so far on my 10.7.4 machine.

What I have found does help is to make sure all of your permissions are

properly setup. I have copied below a procedure for making sure all of

the permissions are properly set to allow EAGLE to modify it's own files.

Here it is:

1. Open a terminal session.

2. Find out where EAGLE's installation directory is located, by default

it should be in the applications folder.

3. Use the cd (change directory) command to work your way to the EAGLE

installation folder.

4. Once your inside EAGLE's installation folder use the ls(list) command

to see the contents of EAGLE's installation directory. You should see

six folders bin, ulp, scr, lbr, doc, and cam.

5. Use the ls -l command to give you a more info on the items. The item

you're interested is the ownership of the file, you'll notice that for

EAGLE's folders the owner is 507 instead of your user id.

6. What you need to do now is change the ownership of the files to your

person. We do this using the chown(change owner) command. The syntax is

as follows:

sudo chown username file1 file2 file3 etc

Since we want to change the ownership of all of the files in the

directory it's easier to use a wildcard instead of the typing in the

folder names one by one. So the syntax you'll want to use is:

sudo chown -Rf username *

7.The -Rf tag tells the command to go through all of the files within

the directory so it will go through all of the folders and directories

under the EAGLE folder at once.

8. You're going to repeat this process now using the chmod command which

controls how various users can access and modify the files. Type the command

sudo chmod -Rf 777 *

9. Once this is done you'll have access to all of EAGLE's files and

you'll be able to modify them without the MAC OS getting in the way.

hth,

Jorge Garcia

Cadsoft Support

I bought it a year ago and am just now using it and it crashes every time I turn around!

I guess other people aren't having this problem or I'd see some activity on

the forum.  Eagle consistently crashes every time I run a CAM job.  It

doesn't happen while the job is running, but usually around 10 or 20

seconds after it's done. I'm using v6.3.  I'm new to Eagle and didn't run

CAM processes in 6.2, so I don't know if it was a problem with that

version.  I'm running on OSX 10.7.5

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.