UNSOLVED Font Info Crash
maximefittes last edited by maximefittes
Hello @frederik, my macOS is 10.14.6.
How can I send you the log file?
Strange... could you me send the log? (offline)
what is your macOS version?
Thanks @gferreira, unfortunatly the problem happens with different fonts. And I didn't mention that RF doesn't crash every time I edit the font info. It seems to happen randomly.
I will check the font info file in case I find something and I will make the upgrade to RF 3.4. I Hope it will work!
gferreira last edited by gferreira
if the problem happens with only one font, it’s probably some bad data in your font info. you can try opening the UFO’s
fontinfo.plistfile in a code editor to check (to view files inside a UFO, right-click it in Finder and choose Show Package Contents). I can also have a look if you send me the UFO.
if the problem happens with every font, then it’s probably something else. have you tried opening the same fonts in RF 3.4?
hope this helps, good luck!
Thanks @gferreira. Unfortunatly, I made a test and when RF crashes due to the Font Info it doesn't appear in the console log. All I have is the Mac system report.
robofont-3-py3.logis the one for RoboFont 3
Thanks again @gferreira for your reply.
Before clearing the contents of the log file, can you tell me if I have to do it in "robofont.log", "robofont-3-py3.log" or both?
hi @maximefittes, thanks for the info.
you can clear the contents of the log file, and then trigger the error again – so the log will contain only the relevant messages. I hope it can give us some clue about what’s the problem.
Thank you for your quick reply @gferreira
• I am using Robofont Version 3.3 (build 1911061105)
• Yes I have many error messages in the file untitled "robofont-3-py3.log" but I don't know which ones are relevant for you.
- which version of RoboFont are you using?
- is there any error message in the console log? (use Ctrl+Alt+Cmd+O to open the log file in Finder)
Hello, I have the same problem of Robofont crashing when I edit the Font Info.
Did you find a solution to avoid that?
could you send the
that one is stored in