CONSTANT crashing Eagle 7.1.0 under MacOS 10.9.4 - is Eagle a real piece of software?

Just checked the new beta 7.5.4 - the same problem

Hi there,

I have the same problem - random crashes every 5-50 min.

Eagle 7.5.0, Mac OS 10.9.5.  I really doubt it is related to the memory - I've got 18Gb and no other apps are running.

If I run an old version 6.6.0 - no problems besides the commonly known screen re-draw issue.

Cheers

Kir

Am 24.04.2016 um 04:01 schrieb Herb Sims:

Jorge,

 

I am having the same problem with V7.5 and Mac El Capitan OS.

 

Here is what is says after more more than 30 seconds of autorouter:

 

| Process:            | EAGLE |

| Path:               |

/Applications/EAGLE-7.5.0/EAGLE.app/Contents/MacOS/EAGLE |

| Identifier:         | EAGLE |

| Version:            | 7.5.0 (7.5.0) |

| Code Type:          | X86-64 (Native) |

| Parent Process:     | ??? |

| Responsible:        | EAGLE |

| User ID:            | 501 |

Could be a memory problem. What are the grid settings for the

Autorouter and the size of the board? How many routing jobs are

running simultaniously?

--

Mit freundlichen Gruessen / Best regards

Richard Hammerl

  CadSoft Support -- hotline@cadsoft.de

  FAQ: http://www.cadsoft.de/training/faq/

Am 24.04.2016 um 04:01 schrieb Herb Sims:

Jorge,

 

I am having the same problem with V7.5 and Mac El Capitan OS.

 

Here is what is says after more more than 30 seconds of autorouter:

 

| Process:            | EAGLE |

| Path:               |

/Applications/EAGLE-7.5.0/EAGLE.app/Contents/MacOS/EAGLE |

| Identifier:         | EAGLE |

| Version:            | 7.5.0 (7.5.0) |

| Code Type:          | X86-64 (Native) |

| Parent Process:     | ??? |

| Responsible:        | EAGLE |

| User ID:            | 501 |

Could be a memory problem. What are the grid settings for the

Autorouter and the size of the board? How many routing jobs are

running simultaniously?

--

Mit freundlichen Gruessen / Best regards

Richard Hammerl

  CadSoft Support -- hotline@cadsoft.de

  FAQ: http://www.cadsoft.de/training/faq/

Am 24.04.2016 um 04:01 schrieb Herb Sims:

Jorge,

 

I am having the same problem with V7.5 and Mac El Capitan OS.

 

Here is what is says after more more than 30 seconds of autorouter:

 

| Process:            | EAGLE |

| Path:               |

/Applications/EAGLE-7.5.0/EAGLE.app/Contents/MacOS/EAGLE |

| Identifier:         | EAGLE |

| Version:            | 7.5.0 (7.5.0) |

| Code Type:          | X86-64 (Native) |

| Parent Process:     | ??? |

| Responsible:        | EAGLE |

| User ID:            | 501 |

Could be a memory problem. What are the grid settings for the

Autorouter and the size of the board? How many routing jobs are

running simultaniously?

--

Mit freundlichen Gruessen / Best regards

Richard Hammerl

  CadSoft Support -- hotline@cadsoft.de

  FAQ: http://www.cadsoft.de/training/faq/

This can be a sign that you ran out of memory. If you are running other processes, please stop them and try again.

Jorge,

I am having the same problem with V7.5 and Mac El Capitan OS.

Here is what is says after more more than 30 seconds of autorouter:

Time Awake Since Boot: 34000 seconds

System Integrity Protection: enabled

VM Regions Near 0x700000531ff8:

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

Thread 1:

Thread 2:: Dispatch queue: com.apple.libdispatch-manager

Thread 3:

Thread 4:

Thread 5:

Thread 6:

Thread 7:

Thread 8:: com.apple.NSEventThread

Thread 9:

Thread 10 Crashed:: Thread (pooled)

Thread 11:: Thread (pooled)

Thread 12:: Thread (pooled)

Thread 13:: Thread (pooled)

Thread 10 crashed with X86 Thread State (64-bit):

  rax: 0x0000000114125fd0  rbx: 0x0000000114125fe0  rcx: 0x0000000113f16e60  rdx: 0x000000011424c800

  rdi: 0x000000010d403900  rsi: 0x0000000113f16da0  rbp: 0x0000700000532010  rsp: 0x0000700000532000

   r8: 0x0000000112f47690   r9: 0x00000000fffff800  r10: 0x000000000ef99735  r11: 0x000000010de00000

  r12: 0x000000010d403930  r13: 0x004990c00024f580  r14: 0x000000010d403900  r15: 0x0000000113f16e00

  rip: 0x000000010003e068  rfl: 0x0000000000010246  cr2: 0x0000700000531ff8

Binary Images:

External Modification Summary:

  Calls made by other processes targeting this process:

  Calls made by this process:

  Calls made by all processes on this machine:

VM Region Summary:

ReadOnly portion of Libraries: Total=239.4M resident=0K(0%) swapped_out_or_unallocated=239.4M(100%)

Writable regions: Total=234.5M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=234.5M(100%)

On 9/17/2014 1:10 AM, Ben Cannon wrote:

Hi Jorge, thank you for chiming in.

 

I mean crashing.  As in, "The application EAGLE unexpectedly quit, click

here to reopen".

 

I see that the top router does take a lot longer, but it does seem to

produce some exciting results.

 

It looks like none of the auto routers are able to route a board of any

complexity that incorporates a ground plane. (Why it doesn't simply add

Vias to reconnect a "fallen apart" ground plane is beyond me.)   Just

auto routing the GND class/net with via cost way down produces a

beautiful result, but as soon as the rest of the board is routed with

ground/VCC planes, everything goes to heck.  But that's another story.

 

I've got to get around these crashes first, it's all but completely

un-useable now, the crashes are 100% now, somewhere between 5 and 15min

into an autoroute (that looks like it should be a multi-hour process

with my settings.)

Hi Ben,

Let's make sure you're permissions for EAGLE are setup correctly first.

The crash time you're talking about 5 to 15 min is close to the

automatic backup generation interval. If EAGLE isn't permitted to

perform the backup, then it will crash.

Here's the procedure to setup EAGLE's permissions

1. Open Finder.

2. Navigate to Application

3. right click on EAGLE-7.1.0 Folder and select “Get Info”

4. left click on the lock symbol at the bottom right and log into your

admin account.

5. select the plus sign on the bottom left and add your login name to

the access list.

6. select your access list the change it to read & write.

7. left click on the lock symbol to close access to permission changes.

hth,

Jorge Garcia

Hi Jorge, thank you for chiming in. 

I mean crashing.  As in, "The application EAGLE unexpectedly quit, click here to reopen". 

I see that the top router does take a lot longer, but it does seem to produce some exciting results.

It looks like none of the auto routers are able to route a board of any complexity that incorporates a ground plane. (Why it doesn't simply add Vias to reconnect a "fallen apart" ground plane is beyond me.)   Just auto routing the GND class/net with via cost way down produces a beautiful result, but as soon as the rest of the board is routed with ground/VCC planes, everything goes to heck.  But that's another story.

I've got to get around these crashes first, it's all but completely un-useable now, the crashes are 100% now, somewhere between 5 and 15min into an autoroute (that looks like it should be a multi-hour process with my settings.)

On 9/15/2014 10:02 PM, Ben Cannon wrote:

I have an urgent project that constantly crashed the autorouter

approximately 90% of the time.  The system is unusable, and while

tweaking the auto router and doing things like routing the ground plane

first eventually produced a 100% route, the polygons subsequently "fall

apart" on my ground plane, completing only 80% of the only fairly

complex board.

 

System has 24 cores at 3.46Ghz and 64GB of ram...

 

Is this software just junk?

 

--

To view any images and attachments in this post, visit:

http://www.element14.com/community/message/126511

 

Hello Ben,

I hope you're doing well. Define "crash", do you mean EAGLE actually

closes or does it just seem to stop working. The pre-router variant can

take a while to process. To test this run the autorouter but uncheck the

prerouter option that shows up in the first dialog after you click on

the autorouter.

Keep in mind that an autorouter is a tool, and being a designer involves

knowing when to use one tool over the other. Polygons fall apart when

too many traces run through them and isolated islands of copper form. If

you have any high-speed or high-power signals don't use the autorouter.

If you have any low level signals to process don't use the autorouter.

Your hardware can't be fully leveraged by EAGLE so past a certain point

having more ram or cores doesn't produce any improvement in processing time.

hth,

Jorge Garcia