Crashes in El Capitan

Georg, you’re saying that I should record my screen full time (cause it happens all the time)?
it happens in all my files, should I send you all of them?

I only need one example. One instances of the crash and the file that it happened with.

It would be really interesting to see what you are doing. I just have opened documents, changed something, closed them for 10 min. And not a single crash.

I will see if that happen again with build 850. The context of those situations were while working with files that contain around 23 thousand glyphs and six masters layers per each window.

I have fixed a crash related to closing windows in 851.

I’ll try to make a screencast for you too. What I basically do is open a font (often just for reference, like looking into the font info.) When I then close it again, it often crashes. Unfortunately just not exactly now. But the last report I sent you half an hour ago was caused by exactly this. Stay tuned …

Did I break the crash reporter in 851? Or why are there no reports yet?

I just sent you one. It had among other reports this bit:

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'An instance 0x7fa524af7c20 of class GSGlyph was deallocated while key value observers were still registered with it. Current observation info: <NSKeyValueObservationInfo 0x7fa5254ac470> (
<NSKeyValueObservance 0x7fa525495290: Observer: 0x7fa525495220, Key path: layers, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x7fa5206f7540>
<NSKeyValueObservance 0x7fa525494f60: Observer: 0x7fa5254a84e0, Key path: name, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x7fa5206f28f0>
<NSKeyValueObservance 0x7fa525495020: Observer: 0x7fa525495150, Key path: leftKerningGroup, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x7fa5206f72d0>
<NSKeyValueObservance 0x7fa5254ac400: Observer: 0x7fa5254a8550, Key path: rightKerningGroup, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x7fa5206f25b0>
<NSKeyValueObservance 0x7fa5254a7360: Observer: 0x7fa5254ac710, Key path: layers, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x7fa5206f7540>
<NSKeyValueObservance 0x7fa5254a73d0: Observer: 0x7fa5254ac850, Key path: colorIndex, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x7fa5206f0c70>
)'

Just sent you one too, tomorrow I’ll do the screencast.

Because it’s a weekend. I just installed 851 and crashed it in under ten seconds by closing a file. I sent a report at 21:29 Mountain Time.

Just to update this topic, I’m with 856 now, less crashes during the day, but not completely stable.

Something I realized – last week I was working on my laptop instead of my iMac, and it crashed less times. I don’t know if make any difference or if it was just luck. Anyway, my iMac is a 27" late 2009, my MacBook Pro is a 15" Early 2011 – working with 870 now.

Do you have the same plugins on both Macs?

I recently reseted my iMac, so, I’m just with RMX Tools – on the MacBook I have RMX, LSCadencer, ShowSiblings and SpeedPunk

Again I have problems with the Preview Panel.

After installing new version(870) the preview panel has issues with updating itself.
It is hard to say when the problem appears:
For instance I was working on digit Two and most of the actions (like moving points etc) didn’t affect the preview panel. Suddenly after moving one of the points preview panel reacted.

after updating new version of rmx tools everything seems fine

Last version (870) crashes when I’m pressing right mouse button on smart component.

870 - I have crashes while going to the OT Features settings, and on export (I have InterpolationWeightY in many instances).

Still using 2.2.2 for the bulk of the work.

873 – still happening

FWIW, 2.2.2 has been crashing less frequently for me lately (I’m on 10.11.4). When it does, the one I get is when quitting after closing a document window. It’s been several days since the last one, and I’ve been working in Glyphs pretty much all day every day for the last week or two.

I think it has something to do with the complexity of the font in 2.2. If I’m working on something very simple, like Latin with no accented characters, 2.2 is usable. With a Latin+Kannada or Latin+Devanagari I’m lucky if I can keep it open long enough to export a font that I built in 875 but 875 can’t export.