Ticket #841 (closed defect: fixed)
FontConfig makes Aegisub freeze on OS X while caching.
| Reported by: | verm | Owned by: | nielsm |
|---|---|---|---|
| Priority: | high | Milestone: | 2.1.8 |
| Component: | Interface | Version: | devel |
| Severity: | block | Keywords: | |
| Cc: | Platform: | OS X | |
| Sub Component: |
Description
There needs to be a progress meter or atleast a dialogue that lets the user know FontConfig is currently caching fonts. This only happens when the cache is initialised after that it's quick.
Attachments
Change History
comment:1 Changed 3 years ago by verm
- Severity changed from minor to block
- Milestone changed from 2.3.0 to 2.2.0
comment:2 Changed 3 years ago by verm
- Milestone changed from 2.1.7 to 2.2.0
Move ticket to milestone:2.2.0 as milestone:2.1.7 became a windows-only maintenance release.
comment:3 Changed 3 years ago by verm
(In [3176]) Update to 9ad13b from the libass git repo. ( http://greg.geekmind.org/viewgit/) This change also includes the ability to split off fontconfig cache updating into it's own step so dialogues can be used to warn the user about the font cache being updated (it can take several mins on slow machines with lots of fonts). Updates #841
comment:4 Changed 2 years ago by verm
- Milestone changed from 2.2.0 to 2.1.8
This needs to be done for milestone:2.1.8
Changed 2 years ago by nielsm
-
attachment
libass_fontupdate_dialog.patch
added
Non-working initial patch to add this dialogue
comment:7 Changed 2 years ago by nielsm
I attached the initial patch I wrote in blind to address this issue. It doesn't work in this state and needs a bunch of fixing.
Changed 2 years ago by nielsm
-
attachment
libass_fontupdate_dialog-2.patch
added
Semi-working patch (builds and mostly works)
comment:8 Changed 2 years ago by nielsm
Attached a new patch that at least almost solves the issue. The updating does happen in the background and the dialogue does show if it takes more than a short while.
Problem is that the dialogue is not modal at all, and also it doesn't centre on the screen as it should.
comment:10 Changed 2 years ago by nielsm
What's blocking this ticket from being closed:
The dialogue box is not modal, at all.
The user can interact with the main UI while the dialogue is up and fonts are being cached, essentially in the middle of another operations. This can potentially cause serious re-entrancy failures.
comment:11 Changed 2 years ago by verm
comment:12 Changed 2 years ago by nielsm
- Status changed from accepted to closed
- Resolution set to fixed
Created #1115 calling for a better solution.
Closing this for 2.1.8.

Set to block and change to milestone:2.2.0 We could probably avoid doing it but I'm sure we'll get a LOT of bug reports about "freezing".