You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(16) |
Apr
(100) |
May
(78) |
Jun
(44) |
Jul
(86) |
Aug
(56) |
Sep
(29) |
Oct
(70) |
Nov
(110) |
Dec
(104) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(189) |
Feb
(77) |
Mar
(90) |
Apr
(101) |
May
(79) |
Jun
(96) |
Jul
(220) |
Aug
(90) |
Sep
(117) |
Oct
(152) |
Nov
(77) |
Dec
(62) |
2006 |
Jan
(71) |
Feb
(149) |
Mar
(144) |
Apr
(156) |
May
(56) |
Jun
(149) |
Jul
(38) |
Aug
(90) |
Sep
(49) |
Oct
(71) |
Nov
(67) |
Dec
(100) |
2007 |
Jan
(76) |
Feb
(52) |
Mar
(73) |
Apr
(96) |
May
(88) |
Jun
(88) |
Jul
(155) |
Aug
(139) |
Sep
(54) |
Oct
(174) |
Nov
(217) |
Dec
(93) |
2008 |
Jan
(125) |
Feb
(161) |
Mar
(69) |
Apr
(54) |
May
(85) |
Jun
(134) |
Jul
(143) |
Aug
(98) |
Sep
(82) |
Oct
(131) |
Nov
(147) |
Dec
(189) |
2009 |
Jan
(61) |
Feb
(71) |
Mar
(86) |
Apr
(51) |
May
(78) |
Jun
(102) |
Jul
(98) |
Aug
(88) |
Sep
(140) |
Oct
(22) |
Nov
(18) |
Dec
(24) |
2010 |
Jan
(11) |
Feb
(43) |
Mar
(23) |
Apr
(39) |
May
(46) |
Jun
(34) |
Jul
(17) |
Aug
(16) |
Sep
(46) |
Oct
(48) |
Nov
(29) |
Dec
(58) |
2011 |
Jan
(35) |
Feb
(83) |
Mar
(41) |
Apr
(33) |
May
(23) |
Jun
(39) |
Jul
(6) |
Aug
(23) |
Sep
(30) |
Oct
(22) |
Nov
(68) |
Dec
(55) |
2012 |
Jan
(43) |
Feb
(40) |
Mar
(28) |
Apr
(9) |
May
(96) |
Jun
(54) |
Jul
(468) |
Aug
(678) |
Sep
(640) |
Oct
(112) |
Nov
(60) |
Dec
(154) |
2013 |
Jan
(113) |
Feb
(50) |
Mar
(74) |
Apr
(17) |
May
(45) |
Jun
(32) |
Jul
(52) |
Aug
(16) |
Sep
(66) |
Oct
(60) |
Nov
(64) |
Dec
(62) |
2014 |
Jan
(43) |
Feb
(25) |
Mar
(29) |
Apr
(9) |
May
(5) |
Jun
(60) |
Jul
(31) |
Aug
(42) |
Sep
(19) |
Oct
(13) |
Nov
(9) |
Dec
(2) |
2015 |
Jan
(45) |
Feb
(29) |
Mar
(8) |
Apr
(2) |
May
(10) |
Jun
(8) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(7) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
(4) |
Apr
(43) |
May
(2) |
Jun
(20) |
Jul
(7) |
Aug
(39) |
Sep
(20) |
Oct
(11) |
Nov
(9) |
Dec
|
2017 |
Jan
(3) |
Feb
|
Mar
(4) |
Apr
(1) |
May
(2) |
Jun
(16) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(10) |
Apr
(1) |
May
(16) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(7) |
2019 |
Jan
(3) |
Feb
(4) |
Mar
(7) |
Apr
(20) |
May
|
Jun
(10) |
Jul
(15) |
Aug
(19) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
(15) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Yuri C. <yu...@uk...> - 2020-01-13 06:40:42
|
понеділок, 13 січня 2020 р. 00:11:16 EET Alexandre Risbud-Vincent написано: > Hello, I just downloaded FontForge and installed it in French, and I > realised there seem to be a lot of errors in the French version. > So I'm just offering myself to help making a better translation if this > help is indeed wanted. > > (Please excuse my bad english...) > Thank you! Hi, What exactly do you want to know? As it was mentioned earlier the source is here: https://github.com/fontforge/fontforge/raw/master/po/fr.po You can edit it (poEdit, Lokalize, gTranslator, Virtaal, OmegaT, gVim plugin, Emacs, etc.) then push it in you fork of FontForge repo on github and create a pull request. Please do not hesitate to ask questions if you need some help. Best regards, Yuri Mageia translation coordinator |
From: Joe <di...@jo...> - 2020-01-12 23:26:42
|
Hi Alexandre, Your help will be appreciated. There may be some translators on this mailing list that may respond, and might help too. However, if not, the files of interest are located in the po directory at: https://github.com/fontforge/fontforge/ There are also additional directories at https://github.com/fontforge/ which involve website pages and more Also, if you go to webpage: https://github.com/fontforge/fontforge/issues/ and search for closed issues with the search term French you may find some other additional information which may help. Ask questions if you get stuck on "How To?". Thanks, Joe |
From: Alexandre Risbud-V. <sim...@gm...> - 2020-01-12 22:11:37
|
Hello, I just downloaded FontForge and installed it in French, and I realised there seem to be a lot of errors in the French version. So I'm just offering myself to help making a better translation if this help is indeed wanted. (Please excuse my bad english...) Thank you! |
From: Martin B. B. <mbr...@al...> - 2019-09-17 16:09:58
|
The outlines should have nothing to do with the spacing. The larger sizes are where the kerning takes effect. Spacing is determined by character widths and kerning. If they’re OK and spacing is still messed up then there’s a flaw in OpenOffice. > Attached to this note is an example of the SVG files that I import from Inkscape. I have a windows 10 computer, and using the FontForge from this last April. > > Anyway, when I generate a true type font, and then attempt to use it in a text document in Open Office, the spacing in the larger sizes gets messed up in which the letters scrunch up together. Then sometimes the whole line practically get all piled on to just the space of one or two letters. Sadly I don't know if this is due faulty translation of an SVG file….. |
From: John H. <jph...@gm...> - 2019-09-17 00:10:32
|
Attached to this note is an example of the SVG files that I import from Inkscape. I have a windows 10 computer, and using the FontForge from this last April. Anyway, when I generate a true type font, and then attempt to use it in a text document in Open Office, the spacing in the larger sizes gets messed up in which the letters scrunch up together. Then sometimes the whole line practically get all piled on to just the space of one or two letters. Sadly I don't know if this is due faulty translation of an SVG file, or if I'm not putting in the right commands somewhere. I tried to find answers on a few forums but to no avail. When I try to use some of the fontforge's fix routines, it totally messes up the characters. However, the generated font seems to work OK in graphics programs. |
From: csabourin <csa...@we...> - 2019-09-10 19:40:54
|
How do i remove glyphs completely from an otf font? I've tried Encoding>detach and remove glyphs but then i get red question marks at the top and when i generate the font, the font appears as boxes. The font has two different styles of numbers: oldstyle and tabular. When i type numbers in a program it automatically selects the oldstyle numbers. I want it to select the tabular numbers instead. How do i do this? -- Sent from: http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: Fred B. <cop...@ki...> - 2019-08-28 07:03:31
|
This is a question for my fellow developers. Let's assume we have a script like this: import fontforge f = fontforge.fonts()[0] f.createChar(ord("A")) f["A"].right_side_bearing = 100 # "32" is a new flag, sf_imagebyreference. f["A"].importOutlines("/home/fred/Workspace/fontforge/B.jpg", 32) I know we can have it run on start up with: $ fontforge -script imp.py -new -quiet (Note GitHub issue №3905.) But is there a way to pop up the GUI before running the script? I can't find one, and I'm doing GUI development work so that's what I want to test. Do you have a way of doing this Jeremy (or anyone else?? |
From: Ben G. <be...@re...> - 2019-08-15 10:25:39
|
I've posted onto github. Could you add a sticky (or something else) to suggest where you want bugs posted? Maybe you did already.. ;-D > On 15 Aug 2019, at 09:16, T J <jt...@ou...> wrote: > > Sorry, I didn’t see this earlier. I’d recommend posting bugs to GitHub for better visibility. > > My suspicion, if it’s faulting in Pango, is to try the latest master build from here: http://dl.bintray.com/fontforge/fontforge/ (scroll to the bottom and pick the last dmg) > > For that release, we had pinned Pango to a specific version to work around another crash, but this may have been causing some other issues since GTK was updated in the mean time (and likely built against a newer Pango). > > We no longer pin Pango, as the fix has been released upstream, so trying the latest build would help to rule that out. > > Thanks, > Jeremy > > From: Skef Iterum <gi...@sk...> > Sent: Wednesday, August 7, 2019 7:03:19 AM > To: fon...@li... <fon...@li...> > Subject: Re: [fontforge-devel] Latest Release crashing - a lot. > > It may be best to downgrade for the time being. Mac problems often last a while because none of the folks who look at bugs regularly have regular access to one. > > Skef > > On 8/6/19 1:55 PM, Ben Griffin wrote: >>>>>> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) >>>>>> >> Oh this is so sad… Sorry. I’ve got to go to bed now. I lost another 30 minutes work to this crash. I should have saved it, I know. >> >> >> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >> >> Exception Type: EXC_BAD_ACCESS (SIGSEGV) >> Exception Codes: KERN_INVALID_ADDRESS at 0x00007ffffffffff0 >> >> Termination Signal: Segmentation fault: 11 >> Termination Reason: Namespace SIGNAL, Code 0xb >> Terminating Process: exc handler [2239] >> >> VM Regions Near 0x7ffffffffff0: >> --> shared memory 00007fffffed5000-00007fffffed6000 [ 4K] r-x/r-x SM=SHM >> >> >> ID Vend/Dev >> 7030 67df1002 >> Seconds Ago ID Type >> 3800.0 7030 Attach >> >> Application Specific Information: >> objc_msgSend() selector name: _cfTypeID >> >> >> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >> 0 libobjc.A.dylib 0x00007fff5759a69d objc_msgSend + 29 >> 1 com.apple.CoreGraphics 0x00007fff2d23abdf assert_check_region + 30 >> 2 com.apple.CoreGraphics 0x00007fff2d2596e3 CGRegionCreateUnionWithRegion + 28 >> 3 com.apple.CoreGraphics 0x00007fff2d2596bb CGSUnionRegion + 14 >> 4 com.apple.AppKit 0x00007fff2a620f25 -[_NSCGSWindowBackingStore dirtyBackBufferInRegion:] + 64 >> 5 com.apple.AppKit 0x00007fff2a6202aa backing_store_delegate + 967 >> 6 com.apple.AppKit 0x00007fff2a93c1e2 backing_store_DrawRects.llvm.2329424099933660171 + 907 >> 7 com.apple.CoreGraphics 0x00007fff2d2411f2 CGContextFillRects + 96 >> 8 com.apple.CoreGraphics 0x00007fff2d24118b CGContextFillRect + 105 >> 9 com.apple.AppKit 0x00007fff2a540568 NSRectFill + 237 >> 10 com.apple.AppKit 0x00007fff2a61fc98 -[NSThemeFrame _drawTransparentTitlebarInRect:] + 78 >> 11 com.apple.AppKit 0x00007fff2a61fba9 -[NSThemeFrame _drawUnifiedToolbar:] + 154 >> 12 com.apple.AppKit 0x00007fff2a61f9aa -[NSThemeFrame _drawTitleBar:] + 83 >> 13 com.apple.AppKit 0x00007fff2a61f94c -[NSThemeFrame _drawFrameInterior:clip:] + 66 >> 14 com.apple.AppKit 0x00007fff2a61f8b8 -[NSThemeFrame drawFrame:] + 806 >> 15 com.apple.AppKit 0x00007fff2a61f470 -[NSFrameView drawRect:] + 703 >> 16 com.apple.AppKit 0x00007fff2a61f1af -[NSThemeFrame drawRect:] + 203 >> 17 com.apple.AppKit 0x00007fff2a54021e _NSViewDrawRect + 66 >> 18 com.apple.AppKit 0x00007fff2a52b05e -[NSView _drawRect:clip:] + 1752 >> 19 com.apple.AppKit 0x00007fff2a528fe1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 5165 >> 20 com.apple.AppKit 0x00007fff2a527b8e -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 65 >> 21 com.apple.AppKit 0x00007fff2a525490 -[NSView _oldDisplayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1893 >> 22 com.apple.AppKit 0x00007fff2a524ac9 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 253 >> 23 com.apple.AppKit 0x00007fff2a5216be -[NSView displayIfNeeded] + 1302 >> 24 com.apple.AppKit 0x00007fff2a51e3ff -[NSWindow displayIfNeeded] + 280 >> 25 com.apple.AppKit 0x00007fff2a51e240 __NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 684 >> 26 com.apple.AppKit 0x00007fff2a519334 NSDisplayCycleObserverInvoke + 162 >> 27 com.apple.AppKit 0x00007fff2a518eb4 NSDisplayCycleFlush + 1030 >> 28 com.apple.QuartzCore 0x00007fff3788a54d CA::Transaction::run_commit_handlers(CATransactionPhase) + 49 >> 29 com.apple.QuartzCore 0x00007fff37889d26 CA::Transaction::commit() + 212 >> 30 com.apple.AppKit 0x00007fff2a51884d __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274 >> 31 com.apple.CoreFoundation 0x00007fff2ce7df28 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 >> 32 com.apple.CoreFoundation 0x00007fff2ce7de5d __CFRunLoopDoObservers + 451 >> 33 com.apple.CoreFoundation 0x00007fff2ce20580 __CFRunLoopRun + 1136 >> 34 com.apple.CoreFoundation 0x00007fff2ce1febe CFRunLoopRunSpecific + 455 >> 35 com.apple.HIToolbox 0x00007fff2c07f1ab RunCurrentEventLoopInMode + 292 >> 36 com.apple.HIToolbox 0x00007fff2c07eded ReceiveNextEventCommon + 355 >> 37 com.apple.HIToolbox 0x00007fff2c07ec76 _BlockUntilNextEventMatchingListInModeWithFilter + 64 >> 38 com.apple.AppKit 0x00007fff2a41779d _DPSNextEvent + 1135 >> 39 com.apple.AppKit 0x00007fff2a41648b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361 >> 40 libgdk-3.0.dylib 0x0000000104c34ffc poll_func + 172 >> 41 libglib-2.0.0.dylib 0x00000001051d5c37 g_main_context_iterate + 343 >> 42 libglib-2.0.0.dylib 0x00000001051d5d14 g_main_context_iteration + 100 >> 43 libgdraw.6.dylib 0x0000000103e2d533 GGDKDrawEventLoop + 131 >> 44 libgdraw.6.dylib 0x0000000103db2941 GDrawEventLoop + 65 >> 45 libfontforgeexe.3.dylib 0x0000000103ba3cf7 fontforge_main + 6583 >> 46 fontforge 0x0000000103958f82 main + 34 >> 47 libdyld.dylib 0x00007fff58d763d5 start + 1 >> >> Thread 1: >> 0 libsystem_kernel.dylib 0x00007fff58eb336e poll + 10 >> 1 libgdk-3.0.dylib 0x0000000104c36141 select_thread_func + 721 >> 2 libsystem_pthread.dylib 0x00007fff58f6a2eb _pthread_body + 126 >> 3 libsystem_pthread.dylib 0x00007fff58f6d249 _pthread_start + 66 >> 4 libsystem_pthread.dylib 0x00007fff58f6940d thread_start + 13 >> >> Thread 2: >> 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 >> >> Thread 3: >> 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 >> >> Thread 4: >> 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 >> >> Thread 5: >> 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 >> >> Thread 0 crashed with X86 Thread State (64-bit): >> rax: 0x00007fffffffffd8 rbx: 0x00007fb879e05fe0 rcx: 0x00007fff880fcfd8 rdx: 0x00007fff575bef18 >> rdi: 0x00007fb879e05fe0 rsi: 0x00007fff2f3b8d8e rbp: 0x00007ffeec2a5000 rsp: 0x00007ffeec2a4fe8 >> r8: 0x00000000879e0878 r9: 0x00000000feffffff r10: 0x00007fffffffffd8 r11: 0x00007fff2f3b8d8e >> r12: 0x00007ffeec2a5058 r13: 0x00007ffeec2a51a0 r14: 0x00007fb879e08770 r15: 0x00007fb8956bfbd0 >> rip: 0x00007fff5759a69d rfl: 0x0000000000010206 cr2: 0x00007ffffffffff0 >> >> Logical CPU: 4 >> Error Code: 0x00000004 >> Trap Number: 14 >> >> >> >> >> >> _______________________________________________ >> fontforge-devel mailing list >> >> fon...@li... >> https://lists.sourceforge.net/lists/listinfo/fontforge-devel >> http://fontforge.10959.n7.nabble.com/Developer-f3.html > _______________________________________________ > fontforge-devel mailing list > fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-devel > http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: T J <jt...@ou...> - 2019-08-15 08:16:36
|
Sorry, I didn’t see this earlier. I’d recommend posting bugs to GitHub for better visibility. My suspicion, if it’s faulting in Pango, is to try the latest master build from here: http://dl.bintray.com/fontforge/fontforge/ (scroll to the bottom and pick the last dmg) For that release, we had pinned Pango to a specific version to work around another crash, but this may have been causing some other issues since GTK was updated in the mean time (and likely built against a newer Pango). We no longer pin Pango, as the fix has been released upstream, so trying the latest build would help to rule that out. Thanks, Jeremy ________________________________ From: Skef Iterum <gi...@sk...> Sent: Wednesday, August 7, 2019 7:03:19 AM To: fon...@li... <fon...@li...> Subject: Re: [fontforge-devel] Latest Release crashing - a lot. It may be best to downgrade for the time being. Mac problems often last a while because none of the folks who look at bugs regularly have regular access to one. Skef On 8/6/19 1:55 PM, Ben Griffin wrote: So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) Oh this is so sad… Sorry. I’ve got to go to bed now. I lost another 30 minutes work to this crash. I should have saved it, I know. Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00007ffffffffff0 Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [2239] VM Regions Near 0x7ffffffffff0: --> shared memory 00007fffffed5000-00007fffffed6000 [ 4K] r-x/r-x SM=SHM ID Vend/Dev 7030 67df1002 Seconds Ago ID Type 3800.0 7030 Attach Application Specific Information: objc_msgSend() selector name: _cfTypeID Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00007fff5759a69d objc_msgSend + 29 1 com.apple.CoreGraphics 0x00007fff2d23abdf assert_check_region + 30 2 com.apple.CoreGraphics 0x00007fff2d2596e3 CGRegionCreateUnionWithRegion + 28 3 com.apple.CoreGraphics 0x00007fff2d2596bb CGSUnionRegion + 14 4 com.apple.AppKit 0x00007fff2a620f25 -[_NSCGSWindowBackingStore dirtyBackBufferInRegion:] + 64 5 com.apple.AppKit 0x00007fff2a6202aa backing_store_delegate + 967 6 com.apple.AppKit 0x00007fff2a93c1e2 backing_store_DrawRects.llvm.2329424099933660171 + 907 7 com.apple.CoreGraphics 0x00007fff2d2411f2 CGContextFillRects + 96 8 com.apple.CoreGraphics 0x00007fff2d24118b CGContextFillRect + 105 9 com.apple.AppKit 0x00007fff2a540568 NSRectFill + 237 10 com.apple.AppKit 0x00007fff2a61fc98 -[NSThemeFrame _drawTransparentTitlebarInRect:] + 78 11 com.apple.AppKit 0x00007fff2a61fba9 -[NSThemeFrame _drawUnifiedToolbar:] + 154 12 com.apple.AppKit 0x00007fff2a61f9aa -[NSThemeFrame _drawTitleBar:] + 83 13 com.apple.AppKit 0x00007fff2a61f94c -[NSThemeFrame _drawFrameInterior:clip:] + 66 14 com.apple.AppKit 0x00007fff2a61f8b8 -[NSThemeFrame drawFrame:] + 806 15 com.apple.AppKit 0x00007fff2a61f470 -[NSFrameView drawRect:] + 703 16 com.apple.AppKit 0x00007fff2a61f1af -[NSThemeFrame drawRect:] + 203 17 com.apple.AppKit 0x00007fff2a54021e _NSViewDrawRect + 66 18 com.apple.AppKit 0x00007fff2a52b05e -[NSView _drawRect:clip:] + 1752 19 com.apple.AppKit 0x00007fff2a528fe1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 5165 20 com.apple.AppKit 0x00007fff2a527b8e -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 65 21 com.apple.AppKit 0x00007fff2a525490 -[NSView _oldDisplayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1893 22 com.apple.AppKit 0x00007fff2a524ac9 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 253 23 com.apple.AppKit 0x00007fff2a5216be -[NSView displayIfNeeded] + 1302 24 com.apple.AppKit 0x00007fff2a51e3ff -[NSWindow displayIfNeeded] + 280 25 com.apple.AppKit 0x00007fff2a51e240 __NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 684 26 com.apple.AppKit 0x00007fff2a519334 NSDisplayCycleObserverInvoke + 162 27 com.apple.AppKit 0x00007fff2a518eb4 NSDisplayCycleFlush + 1030 28 com.apple.QuartzCore 0x00007fff3788a54d CA::Transaction::run_commit_handlers(CATransactionPhase) + 49 29 com.apple.QuartzCore 0x00007fff37889d26 CA::Transaction::commit() + 212 30 com.apple.AppKit 0x00007fff2a51884d __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274 31 com.apple.CoreFoundation 0x00007fff2ce7df28 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 32 com.apple.CoreFoundation 0x00007fff2ce7de5d __CFRunLoopDoObservers + 451 33 com.apple.CoreFoundation 0x00007fff2ce20580 __CFRunLoopRun + 1136 34 com.apple.CoreFoundation 0x00007fff2ce1febe CFRunLoopRunSpecific + 455 35 com.apple.HIToolbox 0x00007fff2c07f1ab RunCurrentEventLoopInMode + 292 36 com.apple.HIToolbox 0x00007fff2c07eded ReceiveNextEventCommon + 355 37 com.apple.HIToolbox 0x00007fff2c07ec76 _BlockUntilNextEventMatchingListInModeWithFilter + 64 38 com.apple.AppKit 0x00007fff2a41779d _DPSNextEvent + 1135 39 com.apple.AppKit 0x00007fff2a41648b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361 40 libgdk-3.0.dylib 0x0000000104c34ffc poll_func + 172 41 libglib-2.0.0.dylib 0x00000001051d5c37 g_main_context_iterate + 343 42 libglib-2.0.0.dylib 0x00000001051d5d14 g_main_context_iteration + 100 43 libgdraw.6.dylib 0x0000000103e2d533 GGDKDrawEventLoop + 131 44 libgdraw.6.dylib 0x0000000103db2941 GDrawEventLoop + 65 45 libfontforgeexe.3.dylib 0x0000000103ba3cf7 fontforge_main + 6583 46 fontforge 0x0000000103958f82 main + 34 47 libdyld.dylib 0x00007fff58d763d5 start + 1 Thread 1: 0 libsystem_kernel.dylib 0x00007fff58eb336e poll + 10 1 libgdk-3.0.dylib 0x0000000104c36141 select_thread_func + 721 2 libsystem_pthread.dylib 0x00007fff58f6a2eb _pthread_body + 126 3 libsystem_pthread.dylib 0x00007fff58f6d249 _pthread_start + 66 4 libsystem_pthread.dylib 0x00007fff58f6940d thread_start + 13 Thread 2: 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 Thread 3: 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 Thread 4: 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 Thread 5: 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x00007fffffffffd8 rbx: 0x00007fb879e05fe0 rcx: 0x00007fff880fcfd8 rdx: 0x00007fff575bef18 rdi: 0x00007fb879e05fe0 rsi: 0x00007fff2f3b8d8e rbp: 0x00007ffeec2a5000 rsp: 0x00007ffeec2a4fe8 r8: 0x00000000879e0878 r9: 0x00000000feffffff r10: 0x00007fffffffffd8 r11: 0x00007fff2f3b8d8e r12: 0x00007ffeec2a5058 r13: 0x00007ffeec2a51a0 r14: 0x00007fb879e08770 r15: 0x00007fb8956bfbd0 rip: 0x00007fff5759a69d rfl: 0x0000000000010206 cr2: 0x00007ffffffffff0 Logical CPU: 4 Error Code: 0x00000004 Trap Number: 14 _______________________________________________ fontforge-devel mailing list fon...@li...<mailto:fon...@li...> https://lists.sourceforge.net/lists/listinfo/fontforge-devel http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: T J <jt...@ou...> - 2019-08-15 08:01:18
|
Hi all, If you build or package FontForge yourself, please be aware that FontForge has now switched to use CMake for its build system. The old build system has been completely removed. The minimum supported CMake version is 3.5.1. Transition instructions may be found here: https://github.com/fontforge/fontforge/wiki/CMake-guide-for-FontForge I would greatly appreciate if you can test this, and report any/all issues that you encounter back to https://github.com/fontforge/fontforge/issues Thanks, Jeremy |
From: Skef I. <gi...@sk...> - 2019-08-09 11:43:18
|
Erno - There should be a https://lists.sourceforge.net/lists/listinfo/fontforge-devel link at the bottom of each message. When you follow that one of the links on that page will let you unsubscribe. fontforge-devel is a discussion list for fontforge developers. There is also fontforge-announce:https://sourceforge.net/projects/fontforge/lists/fontforge-announce , a very low volume list which (sometimes) notes new releases of FontForge. Skef On 8/9/19 4:19 AM, Erno Veen wrote: > > Hi Guys > I appreciate that you like to keep people informed, but I'm receiving > far too many updates from you. Is there any way I can unsubscribe? > Thanks > Erno > ------------------------------------------------------------------------ > *From:* T J <jt...@ou...> > *Sent:* 09 July 2019 11:28 > *To:* FontForge developers' discussions > <fon...@li...> > *Subject:* Re: [fontforge-devel] Build system changes > > This is incorrect. CMake is pretty widely supported, and it definitely > has 32-bit support. > > ------------------------------------------------------------------------ > *From:* Joe <di...@jo...> > *Sent:* Tuesday, July 9, 2019 7:35:21 PM > *To:* FontForge developers' discussions > *Subject:* Re: [fontforge-devel] Build system changes > Looking at CMAKE it appears it only supports a limited set of choices. > For example, I'm currently travelling with a mini laptop and I don't > see 32 bit as a choice. > > > _______________________________________________ > fontforge-devel mailing list > fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-devel > http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: Erno V. <ern...@ho...> - 2019-08-09 11:19:18
|
Hi Guys I appreciate that you like to keep people informed, but I'm receiving far too many updates from you. Is there any way I can unsubscribe? Thanks Erno ________________________________ From: T J <jt...@ou...> Sent: 09 July 2019 11:28 To: FontForge developers' discussions <fon...@li...> Subject: Re: [fontforge-devel] Build system changes This is incorrect. CMake is pretty widely supported, and it definitely has 32-bit support. ________________________________ From: Joe <di...@jo...> Sent: Tuesday, July 9, 2019 7:35:21 PM To: FontForge developers' discussions Subject: Re: [fontforge-devel] Build system changes Looking at CMAKE it appears it only supports a limited set of choices. For example, I'm currently travelling with a mini laptop and I don't see 32 bit as a choice. |
From: Skef I. <gi...@sk...> - 2019-08-06 21:03:29
|
It may be best to downgrade for the time being. Mac problems often last a while because none of the folks who look at bugs regularly have regular access to one. Skef On 8/6/19 1:55 PM, Ben Griffin wrote: >>>>> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) > Oh this is so sad… Sorry. I’ve got to go to bed now. I lost another 30 minutes work to this crash. I should have saved it, I know. > > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x00007ffffffffff0 > > Termination Signal: Segmentation fault: 11 > Termination Reason: Namespace SIGNAL, Code 0xb > Terminating Process: exc handler [2239] > > VM Regions Near 0x7ffffffffff0: > --> shared memory 00007fffffed5000-00007fffffed6000 [ 4K] r-x/r-x SM=SHM > > > ID Vend/Dev > 7030 67df1002 > Seconds Ago ID Type > 3800.0 7030 Attach > > Application Specific Information: > objc_msgSend() selector name: _cfTypeID > > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 libobjc.A.dylib 0x00007fff5759a69d objc_msgSend + 29 > 1 com.apple.CoreGraphics 0x00007fff2d23abdf assert_check_region + 30 > 2 com.apple.CoreGraphics 0x00007fff2d2596e3 CGRegionCreateUnionWithRegion + 28 > 3 com.apple.CoreGraphics 0x00007fff2d2596bb CGSUnionRegion + 14 > 4 com.apple.AppKit 0x00007fff2a620f25 -[_NSCGSWindowBackingStore dirtyBackBufferInRegion:] + 64 > 5 com.apple.AppKit 0x00007fff2a6202aa backing_store_delegate + 967 > 6 com.apple.AppKit 0x00007fff2a93c1e2 backing_store_DrawRects.llvm.2329424099933660171 + 907 > 7 com.apple.CoreGraphics 0x00007fff2d2411f2 CGContextFillRects + 96 > 8 com.apple.CoreGraphics 0x00007fff2d24118b CGContextFillRect + 105 > 9 com.apple.AppKit 0x00007fff2a540568 NSRectFill + 237 > 10 com.apple.AppKit 0x00007fff2a61fc98 -[NSThemeFrame _drawTransparentTitlebarInRect:] + 78 > 11 com.apple.AppKit 0x00007fff2a61fba9 -[NSThemeFrame _drawUnifiedToolbar:] + 154 > 12 com.apple.AppKit 0x00007fff2a61f9aa -[NSThemeFrame _drawTitleBar:] + 83 > 13 com.apple.AppKit 0x00007fff2a61f94c -[NSThemeFrame _drawFrameInterior:clip:] + 66 > 14 com.apple.AppKit 0x00007fff2a61f8b8 -[NSThemeFrame drawFrame:] + 806 > 15 com.apple.AppKit 0x00007fff2a61f470 -[NSFrameView drawRect:] + 703 > 16 com.apple.AppKit 0x00007fff2a61f1af -[NSThemeFrame drawRect:] + 203 > 17 com.apple.AppKit 0x00007fff2a54021e _NSViewDrawRect + 66 > 18 com.apple.AppKit 0x00007fff2a52b05e -[NSView _drawRect:clip:] + 1752 > 19 com.apple.AppKit 0x00007fff2a528fe1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 5165 > 20 com.apple.AppKit 0x00007fff2a527b8e -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 65 > 21 com.apple.AppKit 0x00007fff2a525490 -[NSView _oldDisplayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1893 > 22 com.apple.AppKit 0x00007fff2a524ac9 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 253 > 23 com.apple.AppKit 0x00007fff2a5216be -[NSView displayIfNeeded] + 1302 > 24 com.apple.AppKit 0x00007fff2a51e3ff -[NSWindow displayIfNeeded] + 280 > 25 com.apple.AppKit 0x00007fff2a51e240 __NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 684 > 26 com.apple.AppKit 0x00007fff2a519334 NSDisplayCycleObserverInvoke + 162 > 27 com.apple.AppKit 0x00007fff2a518eb4 NSDisplayCycleFlush + 1030 > 28 com.apple.QuartzCore 0x00007fff3788a54d CA::Transaction::run_commit_handlers(CATransactionPhase) + 49 > 29 com.apple.QuartzCore 0x00007fff37889d26 CA::Transaction::commit() + 212 > 30 com.apple.AppKit 0x00007fff2a51884d __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274 > 31 com.apple.CoreFoundation 0x00007fff2ce7df28 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 > 32 com.apple.CoreFoundation 0x00007fff2ce7de5d __CFRunLoopDoObservers + 451 > 33 com.apple.CoreFoundation 0x00007fff2ce20580 __CFRunLoopRun + 1136 > 34 com.apple.CoreFoundation 0x00007fff2ce1febe CFRunLoopRunSpecific + 455 > 35 com.apple.HIToolbox 0x00007fff2c07f1ab RunCurrentEventLoopInMode + 292 > 36 com.apple.HIToolbox 0x00007fff2c07eded ReceiveNextEventCommon + 355 > 37 com.apple.HIToolbox 0x00007fff2c07ec76 _BlockUntilNextEventMatchingListInModeWithFilter + 64 > 38 com.apple.AppKit 0x00007fff2a41779d _DPSNextEvent + 1135 > 39 com.apple.AppKit 0x00007fff2a41648b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361 > 40 libgdk-3.0.dylib 0x0000000104c34ffc poll_func + 172 > 41 libglib-2.0.0.dylib 0x00000001051d5c37 g_main_context_iterate + 343 > 42 libglib-2.0.0.dylib 0x00000001051d5d14 g_main_context_iteration + 100 > 43 libgdraw.6.dylib 0x0000000103e2d533 GGDKDrawEventLoop + 131 > 44 libgdraw.6.dylib 0x0000000103db2941 GDrawEventLoop + 65 > 45 libfontforgeexe.3.dylib 0x0000000103ba3cf7 fontforge_main + 6583 > 46 fontforge 0x0000000103958f82 main + 34 > 47 libdyld.dylib 0x00007fff58d763d5 start + 1 > > Thread 1: > 0 libsystem_kernel.dylib 0x00007fff58eb336e poll + 10 > 1 libgdk-3.0.dylib 0x0000000104c36141 select_thread_func + 721 > 2 libsystem_pthread.dylib 0x00007fff58f6a2eb _pthread_body + 126 > 3 libsystem_pthread.dylib 0x00007fff58f6d249 _pthread_start + 66 > 4 libsystem_pthread.dylib 0x00007fff58f6940d thread_start + 13 > > Thread 2: > 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 > > Thread 3: > 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 > > Thread 4: > 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 > > Thread 5: > 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 > > Thread 0 crashed with X86 Thread State (64-bit): > rax: 0x00007fffffffffd8 rbx: 0x00007fb879e05fe0 rcx: 0x00007fff880fcfd8 rdx: 0x00007fff575bef18 > rdi: 0x00007fb879e05fe0 rsi: 0x00007fff2f3b8d8e rbp: 0x00007ffeec2a5000 rsp: 0x00007ffeec2a4fe8 > r8: 0x00000000879e0878 r9: 0x00000000feffffff r10: 0x00007fffffffffd8 r11: 0x00007fff2f3b8d8e > r12: 0x00007ffeec2a5058 r13: 0x00007ffeec2a51a0 r14: 0x00007fb879e08770 r15: 0x00007fb8956bfbd0 > rip: 0x00007fff5759a69d rfl: 0x0000000000010206 cr2: 0x00007ffffffffff0 > > Logical CPU: 4 > Error Code: 0x00000004 > Trap Number: 14 > > > > _______________________________________________ > fontforge-devel mailing list > fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-devel > http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: Ben G. <be...@re...> - 2019-08-06 20:56:00
|
>>>> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) Oh this is so sad… Sorry. I’ve got to go to bed now. I lost another 30 minutes work to this crash. I should have saved it, I know. Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00007ffffffffff0 Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [2239] VM Regions Near 0x7ffffffffff0: --> shared memory 00007fffffed5000-00007fffffed6000 [ 4K] r-x/r-x SM=SHM ID Vend/Dev 7030 67df1002 Seconds Ago ID Type 3800.0 7030 Attach Application Specific Information: objc_msgSend() selector name: _cfTypeID Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00007fff5759a69d objc_msgSend + 29 1 com.apple.CoreGraphics 0x00007fff2d23abdf assert_check_region + 30 2 com.apple.CoreGraphics 0x00007fff2d2596e3 CGRegionCreateUnionWithRegion + 28 3 com.apple.CoreGraphics 0x00007fff2d2596bb CGSUnionRegion + 14 4 com.apple.AppKit 0x00007fff2a620f25 -[_NSCGSWindowBackingStore dirtyBackBufferInRegion:] + 64 5 com.apple.AppKit 0x00007fff2a6202aa backing_store_delegate + 967 6 com.apple.AppKit 0x00007fff2a93c1e2 backing_store_DrawRects.llvm.2329424099933660171 + 907 7 com.apple.CoreGraphics 0x00007fff2d2411f2 CGContextFillRects + 96 8 com.apple.CoreGraphics 0x00007fff2d24118b CGContextFillRect + 105 9 com.apple.AppKit 0x00007fff2a540568 NSRectFill + 237 10 com.apple.AppKit 0x00007fff2a61fc98 -[NSThemeFrame _drawTransparentTitlebarInRect:] + 78 11 com.apple.AppKit 0x00007fff2a61fba9 -[NSThemeFrame _drawUnifiedToolbar:] + 154 12 com.apple.AppKit 0x00007fff2a61f9aa -[NSThemeFrame _drawTitleBar:] + 83 13 com.apple.AppKit 0x00007fff2a61f94c -[NSThemeFrame _drawFrameInterior:clip:] + 66 14 com.apple.AppKit 0x00007fff2a61f8b8 -[NSThemeFrame drawFrame:] + 806 15 com.apple.AppKit 0x00007fff2a61f470 -[NSFrameView drawRect:] + 703 16 com.apple.AppKit 0x00007fff2a61f1af -[NSThemeFrame drawRect:] + 203 17 com.apple.AppKit 0x00007fff2a54021e _NSViewDrawRect + 66 18 com.apple.AppKit 0x00007fff2a52b05e -[NSView _drawRect:clip:] + 1752 19 com.apple.AppKit 0x00007fff2a528fe1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 5165 20 com.apple.AppKit 0x00007fff2a527b8e -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 65 21 com.apple.AppKit 0x00007fff2a525490 -[NSView _oldDisplayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1893 22 com.apple.AppKit 0x00007fff2a524ac9 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 253 23 com.apple.AppKit 0x00007fff2a5216be -[NSView displayIfNeeded] + 1302 24 com.apple.AppKit 0x00007fff2a51e3ff -[NSWindow displayIfNeeded] + 280 25 com.apple.AppKit 0x00007fff2a51e240 __NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 684 26 com.apple.AppKit 0x00007fff2a519334 NSDisplayCycleObserverInvoke + 162 27 com.apple.AppKit 0x00007fff2a518eb4 NSDisplayCycleFlush + 1030 28 com.apple.QuartzCore 0x00007fff3788a54d CA::Transaction::run_commit_handlers(CATransactionPhase) + 49 29 com.apple.QuartzCore 0x00007fff37889d26 CA::Transaction::commit() + 212 30 com.apple.AppKit 0x00007fff2a51884d __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274 31 com.apple.CoreFoundation 0x00007fff2ce7df28 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 32 com.apple.CoreFoundation 0x00007fff2ce7de5d __CFRunLoopDoObservers + 451 33 com.apple.CoreFoundation 0x00007fff2ce20580 __CFRunLoopRun + 1136 34 com.apple.CoreFoundation 0x00007fff2ce1febe CFRunLoopRunSpecific + 455 35 com.apple.HIToolbox 0x00007fff2c07f1ab RunCurrentEventLoopInMode + 292 36 com.apple.HIToolbox 0x00007fff2c07eded ReceiveNextEventCommon + 355 37 com.apple.HIToolbox 0x00007fff2c07ec76 _BlockUntilNextEventMatchingListInModeWithFilter + 64 38 com.apple.AppKit 0x00007fff2a41779d _DPSNextEvent + 1135 39 com.apple.AppKit 0x00007fff2a41648b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361 40 libgdk-3.0.dylib 0x0000000104c34ffc poll_func + 172 41 libglib-2.0.0.dylib 0x00000001051d5c37 g_main_context_iterate + 343 42 libglib-2.0.0.dylib 0x00000001051d5d14 g_main_context_iteration + 100 43 libgdraw.6.dylib 0x0000000103e2d533 GGDKDrawEventLoop + 131 44 libgdraw.6.dylib 0x0000000103db2941 GDrawEventLoop + 65 45 libfontforgeexe.3.dylib 0x0000000103ba3cf7 fontforge_main + 6583 46 fontforge 0x0000000103958f82 main + 34 47 libdyld.dylib 0x00007fff58d763d5 start + 1 Thread 1: 0 libsystem_kernel.dylib 0x00007fff58eb336e poll + 10 1 libgdk-3.0.dylib 0x0000000104c36141 select_thread_func + 721 2 libsystem_pthread.dylib 0x00007fff58f6a2eb _pthread_body + 126 3 libsystem_pthread.dylib 0x00007fff58f6d249 _pthread_start + 66 4 libsystem_pthread.dylib 0x00007fff58f6940d thread_start + 13 Thread 2: 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 Thread 3: 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 Thread 4: 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 Thread 5: 0 libsystem_pthread.dylib 0x00007fff58f693f0 start_wqthread + 0 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x00007fffffffffd8 rbx: 0x00007fb879e05fe0 rcx: 0x00007fff880fcfd8 rdx: 0x00007fff575bef18 rdi: 0x00007fb879e05fe0 rsi: 0x00007fff2f3b8d8e rbp: 0x00007ffeec2a5000 rsp: 0x00007ffeec2a4fe8 r8: 0x00000000879e0878 r9: 0x00000000feffffff r10: 0x00007fffffffffd8 r11: 0x00007fff2f3b8d8e r12: 0x00007ffeec2a5058 r13: 0x00007ffeec2a51a0 r14: 0x00007fb879e08770 r15: 0x00007fb8956bfbd0 rip: 0x00007fff5759a69d rfl: 0x0000000000010206 cr2: 0x00007ffffffffff0 Logical CPU: 4 Error Code: 0x00000004 Trap Number: 14 |
From: Ben G. <be...@re...> - 2019-08-06 20:24:24
|
I opened the app via a console and I got these Pango Warnings - but I’m not sure they are relevant. I cannot seem to locate where that particular case may be. (fontforge:1776): Pango-WARNING **: 21:02:59.376: Invalid UTF-8 string passed to pango_layout_set_text() (fontforge:1776): Pango-WARNING **: 21:02:59.446: shaping failure, expect ugly output. shape-engine='PangoCoreTextShapeEngine', font='Helvetica', text='\xff\xff\xff' (fontforge:1776): Pango-WARNING **: 21:02:59.473: Invalid UTF-8 string passed to pango_layout_set_text() (fontforge:1776): Pango-WARNING **: 21:03:04.340: Invalid UTF-8 string passed to pango_layout_set_text() (fontforge:1776): Pango-WARNING **: 21:03:04.340: Invalid UTF-8 string passed to pango_layout_set_text() Segmentation fault: 11 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00007fd600000064 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [1776] External Modification Warnings: Thread creation by external task. VM Regions Near 0x7fd600000064: Stack 000070000a909000-000070000a98b000 [ 520K] rw-/rwx SM=NUL thread 6 --> MALLOC_TINY 00007fd670400000-00007fd670800000 [ 4096K] rw-/rwx SM=COW ID Vend/Dev 7030 67df1002 Seconds Ago ID Type 840.0 7030 Attach Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.CoreGraphics 0x00007fff2d27ef88 CGFontStrikeGetValue + 88 1 com.apple.CoreGraphics 0x00007fff2d27ebf0 CGGlyphBuilder::lock_glyph_bitmaps(CGGlyphIdentifier const*, unsigned long, CGGlyphBitmap const**) + 118 2 com.apple.CoreGraphics 0x00007fff2d27ea40 render_glyphs + 184 3 com.apple.CoreGraphics 0x00007fff2d27e243 draw_glyph_bitmaps + 1093 4 com.apple.CoreGraphics 0x00007fff2d27dd70 ripc_DrawGlyphs + 1451 5 com.apple.CoreGraphics 0x00007fff2d27d42f CGContextDelegateDrawGlyphs + 906 6 com.apple.CoreGraphics 0x00007fff2d2ae530 dle_ExecuteDisplayList + 4204 7 com.apple.CoreGraphics 0x00007fff2d2acf7d dle_Execute + 328 8 com.apple.CoreGraphics 0x00007fff2d2acb44 CGDisplayListDrawInContextDelegate + 489 9 com.apple.AppKit 0x00007fff2a581569 -[NSTextLayer drawLayer:inContext:] + 330 10 com.apple.QuartzCore 0x00007fff378b1577 -[CALayer drawInContext:] + 281 11 com.apple.QuartzCore 0x00007fff3789de02 CABackingStoreUpdate_ + 577 12 com.apple.QuartzCore 0x00007fff378ffa0d invocation function for block in CA::Layer::display_() + 53 13 com.apple.QuartzCore 0x00007fff3789db75 x_blame_allocations + 81 14 com.apple.QuartzCore 0x00007fff3789d020 -[CALayer _display] + 1830 15 com.apple.AppKit 0x00007fff2a53d74e _NSBackingLayerDisplay + 528 16 com.apple.QuartzCore 0x00007fff3789c551 CA::Layer::display_if_needed(CA::Transaction*) + 627 17 com.apple.QuartzCore 0x00007fff3788a7c6 CA::Context::commit_transaction(CA::Transaction*) + 342 18 com.apple.QuartzCore 0x00007fff37889ea6 CA::Transaction::commit() + 596 19 com.apple.AppKit 0x00007fff2a51884d __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274 20 com.apple.CoreFoundation 0x00007fff2ce7df28 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 21 com.apple.CoreFoundation 0x00007fff2ce7de5d __CFRunLoopDoObservers + 451 22 com.apple.CoreFoundation 0x00007fff2ce20580 __CFRunLoopRun + 1136 23 com.apple.CoreFoundation 0x00007fff2ce1febe CFRunLoopRunSpecific + 455 24 com.apple.HIToolbox 0x00007fff2c07f1ab RunCurrentEventLoopInMode + 292 25 com.apple.HIToolbox 0x00007fff2c07eded ReceiveNextEventCommon + 355 26 com.apple.HIToolbox 0x00007fff2c07ec76 _BlockUntilNextEventMatchingListInModeWithFilter + 64 27 com.apple.AppKit 0x00007fff2a41779d _DPSNextEvent + 1135 28 com.apple.AppKit 0x00007fff2a41648b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361 29 libgdk-3.0.dylib 0x000000010d351ffc poll_func + 172 30 libglib-2.0.0.dylib 0x000000010d8e4c37 g_main_context_iterate + 343 31 libglib-2.0.0.dylib 0x000000010d8e4d14 g_main_context_iteration + 100 32 libgdraw.6.dylib 0x000000010c553533 GGDKDrawEventLoop + 131 33 libgdraw.6.dylib 0x000000010c4d8941 GDrawEventLoop + 65 34 libfontforgeexe.3.dylib 0x000000010c2cccf7 fontforge_main + 6583 35 fontforge 0x000000010c085f82 main + 34 36 libdyld.dylib 0x00007fff58d763d5 start + 1 |
From: Ben G. <be...@re...> - 2019-08-06 19:39:02
|
And another crash - not libPango. I’m only sending those which have different stack traces… I would help more if you can tell me.. But I cannot build the app from scratch - I just don’t have enough time to set up the full toolchain for that. >>>> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) >>>> The crash seems to be within some call stack of libPango - the actual trace is at home, so I will post it later. Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [21714] VM Regions Near 0x7fff00000060: Stack 00007ffee3728000-00007ffee3f28000 [ 8192K] rw-/rwx SM=SHM thread 0 --> Submap 00007fff00000000-00007fff80000000 [ 2.0G] r--/rwx SM=SHM machine-wide VM submap unused shlib __TEXT 00007fff462da000-00007fff4670c000 [ 4296K] r-x/r-x SM=COW system shared lib __TEXT not used by this process ID Vend/Dev 7030 67df1002 Seconds Ago ID Type 890000.0 7030 Attach Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.CoreGraphics 0x00007fff52000a50 RIPLayerRelease + 13 1 com.apple.CoreGraphics 0x00007fff51ff6bcb ripc_GetClipState + 399 2 com.apple.CoreGraphics 0x00007fff51ff6662 ripc_GetRenderingState + 150 3 com.apple.CoreGraphics 0x00007fff51ff648d ripc_DrawRects + 80 4 com.apple.AppKit 0x00007fff4f4650d1 __backing_store_DrawRects_block_invoke + 39 5 com.apple.AppKit 0x00007fff4f464460 backing_store_delegate + 893 6 com.apple.AppKit 0x00007fff4f78031a backing_store_DrawRects.llvm.1485844590212887067 + 907 7 com.apple.CoreGraphics 0x00007fff51ff63ae CGContextFillRects + 96 8 com.apple.CoreGraphics 0x00007fff51ff6347 CGContextFillRect + 105 9 com.apple.AppKit 0x00007fff4f384768 NSRectFill + 237 10 com.apple.AppKit 0x00007fff4f463e98 -[NSThemeFrame _drawTransparentTitlebarInRect:] + 78 11 com.apple.AppKit 0x00007fff4f463da9 -[NSThemeFrame _drawUnifiedToolbar:] + 154 12 com.apple.AppKit 0x00007fff4f463baa -[NSThemeFrame _drawTitleBar:] + 83 13 com.apple.AppKit 0x00007fff4f463b4c -[NSThemeFrame _drawFrameInterior:clip:] + 66 14 com.apple.AppKit 0x00007fff4f463ab8 -[NSThemeFrame drawFrame:] + 806 15 com.apple.AppKit 0x00007fff4f463670 -[NSFrameView drawRect:] + 703 16 com.apple.AppKit 0x00007fff4f4633af -[NSThemeFrame drawRect:] + 203 17 com.apple.AppKit 0x00007fff4f38441e _NSViewDrawRect + 66 18 com.apple.AppKit 0x00007fff4f36f25e -[NSView _drawRect:clip:] + 1752 19 com.apple.AppKit 0x00007fff4f36d1e1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 5165 20 com.apple.AppKit 0x00007fff4f36bd8e -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 65 21 com.apple.AppKit 0x00007fff4f369690 -[NSView _oldDisplayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1893 22 com.apple.AppKit 0x00007fff4f368cc9 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 253 23 com.apple.AppKit 0x00007fff4f3658be -[NSView displayIfNeeded] + 1302 24 com.apple.AppKit 0x00007fff4f3625ff -[NSWindow displayIfNeeded] + 280 25 com.apple.AppKit 0x00007fff4f362440 __NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 684 26 com.apple.AppKit 0x00007fff4f35d534 NSDisplayCycleObserverInvoke + 162 27 com.apple.AppKit 0x00007fff4f35d0b4 NSDisplayCycleFlush + 1030 28 com.apple.QuartzCore 0x00007fff5c643003 CA::Transaction::run_commit_handlers(CATransactionPhase) + 49 29 com.apple.QuartzCore 0x00007fff5c64274b CA::Transaction::commit() + 213 30 com.apple.AppKit 0x00007fff4f35ca4d __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274 31 com.apple.CoreFoundation 0x00007fff51c33928 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 32 com.apple.CoreFoundation 0x00007fff51c3385d __CFRunLoopDoObservers + 451 33 com.apple.CoreFoundation 0x00007fff51bd5f80 __CFRunLoopRun + 1136 34 com.apple.CoreFoundation 0x00007fff51bd58be CFRunLoopRunSpecific + 455 35 com.apple.HIToolbox 0x00007fff50ec196b RunCurrentEventLoopInMode + 292 36 com.apple.HIToolbox 0x00007fff50ec15ad ReceiveNextEventCommon + 355 37 com.apple.HIToolbox 0x00007fff50ec1436 _BlockUntilNextEventMatchingListInModeWithFilter + 64 38 com.apple.AppKit 0x00007fff4f25b987 _DPSNextEvent + 965 39 com.apple.AppKit 0x00007fff4f25a71f -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361 40 libgdk-3.0.dylib 0x000000010cf9fffc poll_func + 172 41 libglib-2.0.0.dylib 0x000000010d53ac37 g_main_context_iterate + 343 42 libglib-2.0.0.dylib 0x000000010d53ad14 g_main_context_iteration + 100 43 libgdraw.6.dylib 0x000000010c1a7533 GGDKDrawEventLoop + 131 44 libgdraw.6.dylib 0x000000010c12c941 GDrawEventLoop + 65 45 libfontforgeexe.3.dylib 0x000000010bf20cf7 fontforge_main + 6583 46 fontforge 0x000000010bcd9f82 main + 34 47 libdyld.dylib 0x00007fff7db043d5 start + 1 |
From: Ben G. <be...@re...> - 2019-08-06 19:31:29
|
>>>> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) >>>> The crash seems to be within some call stack of libPango - the actual trace is at home, so I will post it later. And another crash - not libPango. Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [21643] ID Vend/Dev 7030 67df1002 Seconds Ago ID Type 890000.0 7030 Attach Application Specific Information: objc_msgSend() selector name: retain Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00007fff7c32869d objc_msgSend + 29 1 com.apple.AppKit 0x00007fff4f4f5033 -[NSApplication(NSWindowCache) _removeWindowFromCache:] + 176 2 com.apple.AppKit 0x00007fff4f4f4eb4 -[NSApplication _removeWindow:] + 453 3 com.apple.AppKit 0x00007fff4fb40a7e -[NSWindow _finishClosingWindow] + 602 4 com.apple.AppKit 0x00007fff4f5d9671 -[NSWindow _close] + 364 5 libgdk-3.0.dylib 0x000000010598b021 gdk_quartz_window_destroy + 369 6 libgdk-3.0.dylib 0x0000000105966e78 _gdk_window_destroy_hierarchy + 1112 7 libgdk-3.0.dylib 0x0000000105966f64 gdk_window_destroy + 20 8 libgdraw.6.dylib 0x0000000104b81348 _GGDKDraw_OnWindowDestroyed + 312 9 libglib-2.0.0.dylib 0x0000000105f102b8 g_timeout_dispatch + 24 10 libglib-2.0.0.dylib 0x0000000105f13956 g_main_context_dispatch + 310 11 libglib-2.0.0.dylib 0x0000000105f13c8d g_main_context_iterate + 429 12 libglib-2.0.0.dylib 0x0000000105f13d14 g_main_context_iteration + 100 13 libgdraw.6.dylib 0x0000000104b84533 GGDKDrawEventLoop + 131 14 libgdraw.6.dylib 0x0000000104b09941 GDrawEventLoop + 65 15 libfontforgeexe.3.dylib 0x00000001048fbcf7 fontforge_main + 6583 16 fontforge 0x00000001046b0f82 main + 34 17 libdyld.dylib 0x00007fff7db043d5 start + 1 |
From: Ben G. <be...@re...> - 2019-08-06 19:29:48
|
>>>> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) >>>> The crash seems to be within some call stack of libPango - the actual trace is at home, so I will post it later. This is another crash - not libPango. Exception Type: EXC_CRASH (SIGABRT) Application Specific Information: abort() called fontforge(21589,0x116efb5c0) malloc: Incorrect checksum for freed object 0x7fd03176fbf0: probably modified after being freed. Corrupt value: 0xb00007fd00000026 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff7dc3f2c6 __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff7dcfabf1 pthread_kill + 284 2 libsystem_c.dylib 0x00007fff7dba96a6 abort + 127 3 libsystem_malloc.dylib 0x00007fff7dcb816b malloc_vreport + 545 4 libsystem_malloc.dylib 0x00007fff7dcd0f01 malloc_zone_error + 183 5 libsystem_malloc.dylib 0x00007fff7dcb4947 tiny_free_list_remove_ptr + 544 6 libsystem_malloc.dylib 0x00007fff7dcb2318 tiny_free_no_lock + 934 7 libsystem_malloc.dylib 0x00007fff7dcb1e75 free_tiny + 480 8 libfontforgeexe.3.dylib 0x000000010cc7ecb3 WordlistEscapedInputStringToParsedDataComplex + 1091 9 libfontforgeexe.3.dylib 0x000000010cc7f3f8 WordlistEscapedInputStringToParsedData + 40 10 libfontforgeexe.3.dylib 0x000000010ca59d1a CV_OnCharSelectorTextChanged + 602 11 libfontforgeexe.3.dylib 0x000000010ca58ad6 CVChangeSC + 2822 12 libfontforgeexe.3.dylib 0x000000010cb5528e FVMouse + 846 13 libfontforgeexe.3.dylib 0x000000010cb5317e v_e_h + 398 14 libgdraw.6.dylib 0x000000010ce646f8 _GWidget_Container_eh + 3048 15 libgdraw.6.dylib 0x000000010cee4e27 _GGDKDraw_CallEHChecked + 135 16 libgdraw.6.dylib 0x000000010cedfa08 _GGDKDraw_DispatchEvent + 5064 17 libgdk-3.0.dylib 0x000000010dcba2a1 _gdk_event_emit + 49 18 libgdk-3.0.dylib 0x000000010dce7652 gdk_event_dispatch + 50 19 libglib-2.0.0.dylib 0x000000010e280956 g_main_context_dispatch + 310 20 libglib-2.0.0.dylib 0x000000010e280c8d g_main_context_iterate + 429 21 libglib-2.0.0.dylib 0x000000010e280d14 g_main_context_iteration + 100 22 libgdraw.6.dylib 0x000000010cee3533 GGDKDrawEventLoop + 131 23 libgdraw.6.dylib 0x000000010ce68941 GDrawEventLoop + 65 24 libfontforgeexe.3.dylib 0x000000010cc57cf7 fontforge_main + 6583 25 fontforge 0x000000010ca0bf82 main + 34 |
From: Ben G. <be...@re...> - 2019-08-06 19:19:53
|
>> There's also a persistent issue with focus on overlapping windows - it may be an x-windows thing but the front window and the active window are not always the same in font-forge, which often leads to strange behaviours - a common issue I have faced is when my active window is behind the the front window and I inadvertently open a menu/submenu which sometimes causes the application to crash. So this is pretty easy to replicate on a Mac. (1) First open a font. (2) Double click on a Glyph (3) Drag the Outline window over the font window. (4) Click back to the font window. (5) Double click on any glyph which will be behind the outline window. — Now the font window is at the back and active, while the outline window (with the new glyph tab and at the front) is inactive. I think this is because the double click is confusing the UI somehow into thinking that the second click may be a focus on the font window after the outline window is opened? |
From: Ben G. <be...@re...> - 2019-08-06 17:11:46
|
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libglib-2.0.0.dylib 0x00000001068ca92c g_slice_alloc + 92 1 libpango-1.0.0.dylib 0x00000001063c7954 pango_font_description_copy_static + 24 2 libpangocairo-1.0.0.dylib 0x00000001063b0c80 pango_core_text_fontset_key_init + 354 3 libpangocairo-1.0.0.dylib 0x00000001063b09ca pango_core_text_font_map_load_fontset + 224 4 libpango-1.0.0.dylib 0x00000001063cd229 itemize_state_process_run + 440 5 libpango-1.0.0.dylib 0x00000001063cccbb pango_itemize_with_base_dir + 110 6 libpango-1.0.0.dylib 0x00000001063d2423 pango_layout_check_lines + 598 7 libpango-1.0.0.dylib 0x00000001063d5e3f pango_layout_get_extents_internal + 47 8 libpango-1.0.0.dylib 0x00000001063d61b3 pango_layout_get_pixel_extents + 71 9 libgdraw.6.dylib 0x0000000105517dea GGDKDrawDoText8 + 202 10 libgdraw.6.dylib 0x000000010549928f GDrawDrawText8 + 111 11 libfontforgeexe.3.dylib 0x0000000105088415 CVInfoDrawText + 1109 12 libfontforgeexe.3.dylib 0x00000001050876bd CVInfoDraw + 29 13 libfontforgeexe.3.dylib 0x000000010509ba2a CVSwitchActiveSC + 1146 14 libfontforgeexe.3.dylib 0x0000000105087f97 CV_OnCharSelectorTextChanged + 1239 15 libfontforgeexe.3.dylib 0x0000000105086ad6 CVChangeSC + 2822 16 libfontforgeexe.3.dylib 0x0000000105093238 CVChangeToFormer + 440 17 libgdraw.6.dylib 0x00000001054e7d52 GTabSetChanged + 82 18 libgdraw.6.dylib 0x00000001054e7782 GTabSetChangeSel + 978 19 libgdraw.6.dylib 0x00000001054e5203 gtabset_mouse + 1619 20 libgdraw.6.dylib 0x0000000105491e5e _GWidget_Container_eh + 846 21 libgdraw.6.dylib 0x0000000105493296 _GWidget_TopLevel_eh + 2550 22 libgdraw.6.dylib 0x0000000105512e27 _GGDKDraw_CallEHChecked + 135 23 libgdraw.6.dylib 0x000000010550da08 _GGDKDraw_DispatchEvent + 5064 24 libgdk-3.0.dylib 0x00000001062e92a1 _gdk_event_emit + 49 25 libgdk-3.0.dylib 0x0000000106316652 gdk_event_dispatch + 50 26 libglib-2.0.0.dylib 0x00000001068ad956 g_main_context_dispatch + 310 27 libglib-2.0.0.dylib 0x00000001068adc8d g_main_context_iterate + 429 28 libglib-2.0.0.dylib 0x00000001068add14 g_main_context_iteration + 100 29 libgdraw.6.dylib 0x0000000105511533 GGDKDrawEventLoop + 131 30 libgdraw.6.dylib 0x0000000105496941 GDrawEventLoop + 65 31 libfontforgeexe.3.dylib 0x0000000105285cf7 fontforge_main + 6583 32 fontforge 0x000000010503cf82 main + 34 |
From: Ben G. <be...@re...> - 2019-08-06 17:09:23
|
Haha- I know, I know. I was just saying I cannot play with / use FF in the office… I meant no offence, and I certainly wouldn’t expect financial gain from my activities with FF! > On 6 Aug 2019, at 16:58, Skef Iterum <gi...@sk...> wrote: > > What a coincidence—I don't get paid to fix bugs in FontForge ... > > Skef > > On 8/6/19 5:36 AM, Ben Griffin wrote: >> (I don't get paid to use FF!). >> >> -B. >> >> >>> On 6 Aug 2019, at 07:38, Skef Iterum <gi...@sk...> <mailto:gi...@sk...> wrote: >>> >>> In your experience are these things that have changed since the previous release or did you switch from an earlier one? >>> >>> Skef >>> >>> On 8/5/19 11:29 PM, Ben Griffin wrote: >>>> Hi, >>>> >>>> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) >>>> The crash seems to be within some call stack of libPango - the actual trace is at home, so I will post it later. >>>> >>>> There's also a persistent issue with focus on overlapping windows - it may be an x-windows thing but the front window and the active window are not always the same in font-forge, which often leads to strange behaviours - a common issue I have faced is when my active window is behind the the front window and I inadvertently open a menu/submenu which sometimes causes the application to crash. >>>> >>>> Another issue is that when there's a deep dependency tree, the source glyph becomes very slow to edit, as it seems all the dependencies are being updated on each edit. It would be awesome if I could turn background updating off - my workaround is to have a proxy dependent glyph which I disconnect from the master glyph - but it is a bit of a headache to have to map (in the current case) 30 or so masters through proxies.. >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> fontforge-devel mailing list >>>> >>>> fon...@li... <mailto:fon...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/fontforge-devel <https://lists.sourceforge.net/lists/listinfo/fontforge-devel> >>>> http://fontforge.10959.n7.nabble.com/Developer-f3.html <http://fontforge.10959.n7.nabble.com/Developer-f3.html> >>> _______________________________________________ >>> fontforge-devel mailing list >>> fon...@li... <mailto:fon...@li...> >>> https://lists.sourceforge.net/lists/listinfo/fontforge-devel <https://lists.sourceforge.net/lists/listinfo/fontforge-devel> >>> http://fontforge.10959.n7.nabble.com/Developer-f3.html <http://fontforge.10959.n7.nabble.com/Developer-f3.html> >> >> >> >> _______________________________________________ >> fontforge-devel mailing list >> fon...@li... <mailto:fon...@li...> >> https://lists.sourceforge.net/lists/listinfo/fontforge-devel <https://lists.sourceforge.net/lists/listinfo/fontforge-devel> >> http://fontforge.10959.n7.nabble.com/Developer-f3.html <http://fontforge.10959.n7.nabble.com/Developer-f3.html> > _______________________________________________ > fontforge-devel mailing list > fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-devel > http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: Skef I. <gi...@sk...> - 2019-08-06 15:59:05
|
What a coincidence—I don't get paid to fix bugs in FontForge ... Skef On 8/6/19 5:36 AM, Ben Griffin wrote: > (I don't get paid to use FF!). > > -B. > > >> On 6 Aug 2019, at 07:38, Skef Iterum<gi...@sk...> wrote: >> >> In your experience are these things that have changed since the previous release or did you switch from an earlier one? >> >> Skef >> >> On 8/5/19 11:29 PM, Ben Griffin wrote: >>> Hi, >>> >>> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) >>> The crash seems to be within some call stack of libPango - the actual trace is at home, so I will post it later. >>> >>> There's also a persistent issue with focus on overlapping windows - it may be an x-windows thing but the front window and the active window are not always the same in font-forge, which often leads to strange behaviours - a common issue I have faced is when my active window is behind the the front window and I inadvertently open a menu/submenu which sometimes causes the application to crash. >>> >>> Another issue is that when there's a deep dependency tree, the source glyph becomes very slow to edit, as it seems all the dependencies are being updated on each edit. It would be awesome if I could turn background updating off - my workaround is to have a proxy dependent glyph which I disconnect from the master glyph - but it is a bit of a headache to have to map (in the current case) 30 or so masters through proxies.. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> fontforge-devel mailing list >>> >>> fon...@li... >>> https://lists.sourceforge.net/lists/listinfo/fontforge-devel >>> http://fontforge.10959.n7.nabble.com/Developer-f3.html >> _______________________________________________ >> fontforge-devel mailing list >> fon...@li... >> https://lists.sourceforge.net/lists/listinfo/fontforge-devel >> http://fontforge.10959.n7.nabble.com/Developer-f3.html > > > _______________________________________________ > fontforge-devel mailing list > fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-devel > http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: Ben G. <be...@re...> - 2019-08-06 12:36:34
|
Hi Skef, The first issue - the many crashes - has changed since I updated from the previous version. The other two issues have persisted across the versions. I can give you more details when I return from the office. (I don't get paid to use FF!). -B. > On 6 Aug 2019, at 07:38, Skef Iterum <gi...@sk...> wrote: > > In your experience are these things that have changed since the previous release or did you switch from an earlier one? > > Skef > > On 8/5/19 11:29 PM, Ben Griffin wrote: >> Hi, >> >> So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) >> The crash seems to be within some call stack of libPango - the actual trace is at home, so I will post it later. >> >> There's also a persistent issue with focus on overlapping windows - it may be an x-windows thing but the front window and the active window are not always the same in font-forge, which often leads to strange behaviours - a common issue I have faced is when my active window is behind the the front window and I inadvertently open a menu/submenu which sometimes causes the application to crash. >> >> Another issue is that when there's a deep dependency tree, the source glyph becomes very slow to edit, as it seems all the dependencies are being updated on each edit. It would be awesome if I could turn background updating off - my workaround is to have a proxy dependent glyph which I disconnect from the master glyph - but it is a bit of a headache to have to map (in the current case) 30 or so masters through proxies.. >> >> >> >> >> >> _______________________________________________ >> fontforge-devel mailing list >> >> fon...@li... >> https://lists.sourceforge.net/lists/listinfo/fontforge-devel >> http://fontforge.10959.n7.nabble.com/Developer-f3.html > _______________________________________________ > fontforge-devel mailing list > fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-devel > http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: Skef I. <gi...@sk...> - 2019-08-06 06:54:12
|
In your experience are these things that have changed since the previous release or did you switch from an earlier one? Skef On 8/5/19 11:29 PM, Ben Griffin wrote: > Hi, > > So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) > The crash seems to be within some call stack of libPango - the actual trace is at home, so I will post it later. > > There's also a persistent issue with focus on overlapping windows - it may be an x-windows thing but the front window and the active window are not always the same in font-forge, which often leads to strange behaviours - a common issue I have faced is when my active window is behind the the front window and I inadvertently open a menu/submenu which sometimes causes the application to crash. > > Another issue is that when there's a deep dependency tree, the source glyph becomes very slow to edit, as it seems all the dependencies are being updated on each edit. It would be awesome if I could turn background updating off - my workaround is to have a proxy dependent glyph which I disconnect from the master glyph - but it is a bit of a headache to have to map (in the current case) 30 or so masters through proxies.. > > > > _______________________________________________ > fontforge-devel mailing list > fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-devel > http://fontforge.10959.n7.nabble.com/Developer-f3.html |
From: Ben G. <be...@re...> - 2019-08-06 06:29:16
|
Hi, So there's a lot of crashes with the latest FF release on Mac OS X (10.14.6) The crash seems to be within some call stack of libPango - the actual trace is at home, so I will post it later. There's also a persistent issue with focus on overlapping windows - it may be an x-windows thing but the front window and the active window are not always the same in font-forge, which often leads to strange behaviours - a common issue I have faced is when my active window is behind the the front window and I inadvertently open a menu/submenu which sometimes causes the application to crash. Another issue is that when there's a deep dependency tree, the source glyph becomes very slow to edit, as it seems all the dependencies are being updated on each edit. It would be awesome if I could turn background updating off - my workaround is to have a proxy dependent glyph which I disconnect from the master glyph - but it is a bit of a headache to have to map (in the current case) 30 or so masters through proxies.. |