Error Message appears constantly when routing in Eagle 9.5.1 on Windows 10

[donHSNHT]

I have a pcb that I have been working on for quite a while across different versions of Eagle. Today the following error message popped up as I was working:

EAGLE has detected an unexpected condition. Please report this error and editing steps prior to this error to Autodesk. If possible, you should save your work to a backup file in case of any data corruption.

Unexpected Condition details: File: ../../src/obstrutils.cpp, Line 604

I have saved the files, closed Eagle completely and reopened the file. The problem persists on this particular board.  I do not see it on other boards so far.

It happens when I try to start routing from an existing trace. Not all nets cause the issue, but quite a few do. When the error pops up, I can hit OK and then continue routing and the routing seems to work. But this message pops up constantly. 

This is making it very difficult to work and I am concerned that the board will suddenly become unusable.

[donHSNHT]

Further update. The problem is related to the layer I am on. If I start a route on layer 16, the message appears. If I am routing and drop a via to layer 16 the message appears.

Don

[jorge_garcia]

Hi @donHSNHT,

Thanks for participating on our forums. That fact that you have a reproducible case is really going to help us solve this. I'm going to DM you my e-mail, if possible please send the files for review and let me know how you reproduce this error.

Let me know if there's anything else I can do for you.

Best Regards,

[Anonymous]

@jorge_garcia has there been a resolution to this yet? I just hit this issue with a board I'm working on...

[Anonymous]

at any rate, it was a pretty simple circuit, so I just built a new board... would have been nice not to lose the work though...

[Anonymous]

Hi @jorge_garcia I experience the same issue on Mac OS X (10.15.2 ). The error message does not show the whole path and I can't seem to find the mentioned file in the finder.

Have you got some info I could use to fix this? 

Thanks!

[one-of-the-robs]

---

@Anonymous wrote:

The error message does not show the whole path and I can't seem to find the mentioned file in the finder.

You won't find the file. That error message is reporting something that shouldn't happen - i.e. not something Eagle can diagnose as being caused by your stuff - and stating where in the code it found it. This information is for Autodesk developers to use and the referenced file is part of the Eagle source code.

[Anonymous]

Oh yes, thank you, that's right this is for debugging purpose, I got it - not sure the error message is super clear but I'm probably too finicky about the user interface.
Now what about the issue itself, I guess I should just ignore it and hope for Eagle not to crash too often [it only crashed 3 times in 2 days :-/] ... has anyone experienced a similar issue? How was it solved if applicable?

[edited for typo]

[jeffg28CLY]

I am also getting this error, Eagle 9.5.2.

I'm trying to start routing on a 2-layer board, starting on Layer 16.

There is a single through-hole pad with both a Layer 1 and Layer 16 trace routed to it already. 

I am in Walkaround Obstacles mode, with Loop Remove enabled, and Wire Bend at the 45° setting.

What's odd is that I already routed 3 other identical objects near this with no errors. Each of them started out as the same type of part: A single through-hole pad with a Layer 1 and Layer 16 trace routed to it. One by one, I routed an additional Layer 16 trace from each. Only on the final one did I start getting this error.

Now every time I click on that trace (or even anywhere on the signal's remaining airwires) to route with Walkaround Obstacles and set to Layer 16, I get the error.

If I start on Layer 1, I do not get the error, but the instant I middle-click to change layers, the error again appears.

Edit: It appears that more traces are now affected as well. Anything dealing with Layer 16 is likely to generate this error. This board has just become unworkable with Walkaround Obstacles enabled.

Edit2: It was a property of some traces I routed. I ripped up a few of the last traces I routed, and the problem seems to have stopped. Something in the traces in those two or three signals is messing with obstrutils.cpp.

I have a backup of the file, and can provide that to Autodesk for analysis.

[dongyang.tang]

I'm having the same issue with Eagle 9.5.1.

It seems all the traces is affected. 

[EricEisele]

I am having the same issue on Windows and OSX with version 9.5.2. Eagle is crashing on me every few minutes. This only happens when routing and avoid obstacles is set. 

[EricEisele]

I am still seeing the same issue in Eagle 9.6.0. It appears to happen only with certain files. Jorge - I have already PM'd you with a link to my file. 

[jorge_garcia]

Hello @EricEisele,

I hope you're doing well. I'll look at the files you sent me. Let me know if there's anything else I can do for you.

Best Regards,

[Anonymous]

I have just started getting this error. I built the same board but mirror yesterday and everything was fine. Do not understand what I could have done to cause this. 

[jesper8W75R]

I have the same issue. Mac OSX, various versions, EAGLE 9.5.0, 9.5.2, 9.6.0
And I have microscopic airwires on ALL wire-to-pad connections.
This is a 5 months old error!!!!!
This REALLY needs to be fixed NOW!
I cannot route my board, and I need to do an urgent update.

[HelenChen-AutodeskQA]

Hi @donHSNHT  et.al,

Sorry to hear that you're having trouble and thank you very much for feedback us.

We just released EAGLE 9.6.1 today which has addressed this issue. Could you please upgrade to 9.6.1 and try again?

Hope it helps and please feel free to let us know if you need our further assistant. 

Thank you.

Regards,

Helen