White screen after launching - crashes?

Bugs
21

Thank you for the additional info :pray:
This is very strange and definitely shouldnā€™t happen.
Is FontBase installed on your local hard drive?

22

yes it is installed on the local hard drive, today after restart it worked again for some minutes, after trying in vain to add fonts, via drag&drop, or with folders, fontbase did not show any new fonts and then it was white againā€¦

23

Thank you for the update :pray:
Just for my better understanding - FontBase worked ok before you added any fonts/folders into it, and then the situation with the white screen repeated itself?

24

at least it was open and displayed, and i can at least activate and deactivate the google fonts, but unfortunately i canā€™t add any other fontsā€¦

25

Thank you for the quick reply :pray:
I do understand that this is a bad situation, and is extremely inconvenient to say the least :pensive:
Iā€™m doing my best to help fix this, but in order to do this I need to understand what is going on and what the cause might be, so the additional information really helps :pray:
For now weā€™ve found out that the freeze happens when you try to add fonts into FontBase.

The fonts youā€™ve added just before the app stopped working - were they on a local hard drive?
What file format were they?

26

a slow answer this time:
Unfortunately, the error occurs even if I donā€™t try to add fonts in vainā€¦ Also when i do nothing the programme gonna white

Font files are .otf or .ttf and yes they are on the local hard drive

27

Thank you for your reply and all the additional information :pray:
In your initial post youā€™ve mentioned that youā€™ve been experiencing this issue for months - would you happen to remember how many, give or take?
Trying to understand if I couldā€™ve been connected to the previous update, or something like an OS update (as was the case with some users here on the forum)

Thank you again,
Yuriy

28

unfortunately i canā€™t reconstruct an exact date, but it has been broken at least since june, more likely longerā€¦

the mac activity display, which shows all processes for fontbase, also looks normal to meā€¦

thanks for you help

29

Thank you for the super-quick reply :pray:
If possible, could you please try to uninstall the current version of FontBase, reset the settings following the guide weā€™ve talked about above, then download the previous FontBase version (2.20.7) and see if the issue would still exist? Please disable auto-updating after this installation to see if the issue is perhaps version-related :pray:

Thank you again,

30

thank you, i will try this, one question so that I do it right: I delete fontbase folder from library, and from the apps, then restart mac and then install?

31

More or less, yes:)
To be precise:

  1. Uninstall the app from your Mac (found an official guide from Apple)
  2. Delete all the local user data contained in ~/Library/Application Support/FontBase and ~/Application Support/FontBase if present, as mentioned in ā€œReset Settingsā€ FontBase guide
  3. Restart the machine just to be sure
  4. Install FontBase

Please let me know how it goes :pray:

Thank you again,
Yuriy

32

Hello!
I have the same issue.
MacOS 13.7.1
MacBook Pro M1
fontbase Ver. 2.21.0

Tried to fix it by installing Ver. 2.20.7 but still same problem.

Do you have any insights, how to fix the problem?

Best
Mehmet

33

Hello Mehmet, thank you for your post and welcome to the forum :pray:
Have you perhaps already had the chance to try the solution mentioned here (including the part about resetting FontBase settings)?

Thank you again,
Yuriy
FontBase Dev Team

34

Thanks for your quick response Yuriy. I tried your solution described here again, including restart. Still get a white screen.

35

Hello Yuriy.
This is the short version of the crash report from MacOs. If you want the full report, get in contact with me, and I can send it to you.
Best
Mehmet

Translated Report (Full Report Below)

Process: FontBase Helper (Renderer) [1421]
Path: /Applications/FontBase.app/Contents/Frameworks/FontBase Helper (Renderer).app/Contents/MacOS/FontBase Helper (Renderer)
Identifier: com.dominiklevitsky.fontbase.helper.Renderer
Version: 2.21.0
Code Type: ARM-64 (Native)
Parent Process: FontBase [1418]
Responsible: FontBase [1418]
User ID: 501

Date/Time: 2024-12-11 10:03:48.7131 +0100
OS Version: macOS 13.7.1 (22H221)
Report Version: 12
Anonymous UUID: 6B99370D-9C33-21C0-6924-2988EC6732C3

Time Awake Since Boot: 1400 seconds

System Integrity Protection: enabled

Crashed Thread: 27 ThreadPoolForegroundWorker

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: FontBase Helper (Renderer) [1421]

Application Specific Information:
abort() called

36

Thank you for the quick reply and the additional information :pray:
Would you happen to remember when this white screen problem started to occur?
What were the changes that preceded this behaviour (e.g. OS/application updates, some folders/fonts added etc)?

Thank you again,
Yuriy

37

Hello Yuriy,
the problem started since 05.12.2024.
If I remember correctly, I did not had updates in MacOS. I remember deactivating some fonts, because the Adobe Fonts didnā€™t updated in Adobe CC Apps correctly and therefore I checked fontbase and realised it had white screens.

38

Thank you for the quick reply :pray:
Thatā€™s odd :thinking:
By ā€œdeactivatingā€ do you mean in FontBase, or in some other way?

39

Hello Yuriy,

I had problems with Adobe Fonts. The fonts could not be activated via the website. Or it took a long time until they were activated. But that has always been the case. I assumed that I had too many other fonts active in Fontbase and then manually deactivated all active fonts. However, I think this is a completely normal process and is not a problem from my point of view. Deactivating fonts in fontbase is a basic function that the program should be able to perform without causing crashes.

I have also tried to start fontbase without an internet connection. The behavior remains the same. Whatever. I can send you the complete crash reports. Unfortunately, I canā€™t post them here because they are too long.

40

Thank you for the quick reply and the additional information :pray:
And thank you for confirming that you meant deactivation via FontBase. And it shouldnā€™t have caused this white screen issue, you are correct.
Would it be possible to try the following:

  1. Uninstall FontBase again.
  2. If you have been using the default Root Folder location - move all the contents to a different folder temporarily, or just rename the Root Folder using your File Explorer to anything other than ā€œFontBaseā€.
  3. Reset FontBase settings again using this guide Reset Settings ā€” FontBase Tutorials.
  4. Re-download the FontBase installer from our website.
  5. Install FontBase.
  6. Launch FontBase.

This way you should have a completely fresh install with only the default pre-loaded Google fonts present in FontBase.
Please let me know if this is possible and whether the white screen issue would still persist :pray:

Thank you again,
Yuriy