Description of problem: FontForge crashed when I tried to create a TTC file, merging four large Japanese fonts. I selected "File" -> "Generate TTC" and clicked "Save." Then FontForge freezed for a few seconds and crashed. It left an empty (zero-byte) TTC file as output. Version-Release number of selected component: fontforge-20120731b-4.fc18 Additional info: backtrace_rating: 4 cmdline: fontforge meiryo001x.ttf meiryo002x.ttf meiryo003x.ttf meiryo004x.ttf crash_function: glyphmatches executable: /usr/bin/fontforge kernel: 3.8.2-206.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 glyphmatches at tottf.c:6454 #2 hashglyphfound at tottf.c:6486 #3 ttc_prep at tottf.c:6621 #4 WriteTTC at tottf.c:7073 #5 DoSave at savefontdlg.c:1587 #6 GFD_exists at savefontdlg.c:1631 #7 _gio_file_statfile at giofile.c:184 #8 _GIO_localDispatch at giofile.c:237 #9 _GFD_SaveOk at savefontdlg.c:1668 #10 GFD_SaveOk at savefontdlg.c:1679
Created attachment 711027 [details] File: backtrace
Created attachment 711028 [details] File: build_ids
Created attachment 711029 [details] File: cgroup
Created attachment 711030 [details] File: core_backtrace
Created attachment 711031 [details] File: dso_list
Created attachment 711032 [details] File: environ
Created attachment 711033 [details] File: limits
Created attachment 711034 [details] File: maps
Created attachment 711035 [details] File: open_fds
Created attachment 711036 [details] File: proc_pid_status
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.