Editing device crashes EAGLE 8

[markus-k]

Hi,

I created a small EAGLE library with two parts yesterday, without any problems. But at some point, EAGLE (8.0.0 and 8.0.1 on Mac OS) started crashing when I try to edit the device, but using the library and editing the symbols still works. Sorta annoying when you want to change something on your part 🙂 I attached the crash report, the library file is available here (no .lbr upload allowed).

Can anyone confirm this behaviour with EAGLE 8? My old EAGLE 7.7 seems to open the file just fine.

Thank you

[jorge_garcia]

Hello markus-k,

I hope you're doing well. Thanks for posting here on the Autodesk Forum. I've informed the devs to take a look at the files you have posted.

We will continue to investigate.

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

Best Regards,

[rachaelATWH4]

I can verify this is definitely a bug in the library editor which I can confirm on macOS Sierra 10.12.3. This has happened with the very first library part I have tried to make in v8 and I come across the bug straight away. I have the latest v8.0.1 installed.

In ECAD tools stability is paramount and EAGLE v7 was rock solid stable for me. In the very short amount of time I have been using EAGLE v8 it's crashed on me several times in the schematic, layout and and now library editor.

This is totally unacceptable and all work on v8 should now be to restore the previous level of stability before going any further with adding features. As things stand v8 is useless to me and I won't be subscribing until I have been convinced that Autodesk has the stability issues back under control.

Best Regards,

Rachael

[jorge_garcia]

Hi Rachael,

I hope you're having a good day. I've been able to reproduce this issue and the devs are working on it diligently. There are at least two other threads discussing this same issue so we are fully aware of it's existence and have been working to remedy it as soon as possible.

Totally understood that there's needs to be proof and some track record to give confidence to our legacy users. Autodesk is committed to improving EAGLE and the fruits of our labor will be seen shortly.

Best Regards,

[rachaelATWH4]

Hi Jorge,

My day has been okay thanks, I didn't lose any work when EAGLE crashed as I had recently saved 🙂 I hope things are going well for you too.

Thanks for the update, I look forward to testing out the next release when it's available. Hopefully it'll resolve all these new stability issues.

Best Regards,

Rachael

[samykamkar]

Hey @rachaelATWH4

If you do experience a crash, you can typically recover the last-modified, unsaved schematic and board files in your project, they're named file.b## and file.s## (only if you made changes without saving -- I think it updates every minute or so?)

I don't mind intermittent crashes given the improvements in functionality and relative ease of recovery.

[rachaelATWH4]

---

@samykamkar wrote:

Hey @rachaelATWH4

If you do experience a crash, you can typically recover the last-modified, unsaved schematic and board files in your project, they're named file.b## and file.s## (only if you made changes without saving -- I think it updates every minute or so?)

I don't mind intermittent crashes given the improvements in functionality and relative ease of recovery.

---

Hiya,

Yes I can go back to intermediate files if needed but I shouldn't have to as it should be more stable than it is. I don't accept that intermittent crashes are ok, what if a particular action that you need to perform is causing the crash and you are stuck and unable to do what you need to do?

Tools which you need to use to do your day job should not crash. If it happens once in a blue moon (i.e. months or years apart) then ok I can accept that occasionally software bugs or incompatibilities cause issues, but if the tool is crashing regularly, I don't care if it auto saved an intermediate file a minute ago, it's not good enough.

I trust in this case though Autodesk will fix the issue but they really do need to ensure better stability for future releases no matter how much extra functionality goes into the tool.

Best Regards,

Rachael

[markus-k]

I just tried EAGLE 8.0.2, still crashes most of the times. It worked once, but when I opened another device it crashed again. New crash reports attached. 

[jorge_garcia]

Hi markus-k,

Thank you for submitting these bug reports, I have attached them to the bug report for this issue. The developers are aware of this issue and it's proving to be sneaky.

I'll post once I have more info.

Best Regards,

[david.mellis]

Hi markus-k,

I've been working on this and related issues caused when switching between devices, packages, and symbols in the library editor. I believe the cause of the crash you're experiencing may be different than the causes of the crashes I've been able to reproduce so far. Are you using Typinator and/or Karabiner or other applications that might be attempting to programmatically access the GUI of the Eagle application (e.g. to provide different keyboard shortcuts or behaviors)? If so, do you get the same crash if you disable those applications?

David

[markus-k]

Hi David,

I had Karabiner running (not even sure what for exactly), but quitting both Karabiner and BetterSnapTool did not help. Still crashes with the QTreeView::isIndexHidden() crash report.

Thank you

[david.mellis]

Hmm... any other similar tools running? Maybe try rebooting after exiting them and see if the problem persists?

If anyone else is reading this, are you seeing crashes with similar function names in the stack traces (e.g. "QTreeView::isIndexHidden(QModelIndex const&)" or "QTreeView::visualRect(QModelIndex const&)" or "[NSObject(NSAccessibilityInternal) _accessibilityAttributeNamesClientError:]")? If so, are you running Typinator and/or Karabiner or other applications that might be attempting to programmatically access the GUI of the Eagle application?