Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freezes after "new" or "open" in Japanese version #19

Closed
tanguband opened this issue Aug 19, 2021 · 7 comments
Closed

Freezes after "new" or "open" in Japanese version #19

tanguband opened this issue Aug 19, 2021 · 7 comments
Labels
bug Something isn't working

Comments

@tanguband
Copy link

3.0.0Alpha35

Environment builds the latest version of the macos-develop branch using macos 11.5.1 commandline tools
Previously the build was successful and it started normally
Freezes when launching a successful build application after several build failures

The screen at the time of freeze is in the following state
please wait
Loading version 3.0.0 save data (SVAE5 format)
Dungeon is being restored

This issue only occurs in the main account and when I switch to the sub account it starts normally
After this state, V2.2.1 and V1.6.2 applications will not start either.

The same phenomenon has occurred with macos14 that I used before.

The error message when booting from terminal is as follows

$ ./hengband
2021-08-19 12: 36: 07.745 hengband [45514: 4719196] *** Assertion failure in-[NSThemeFrame initWithFrame:], NSView.m: 1353
2021-08-19 12: 36: 07.748 hengband [45514: 4719196] Frame containing non-finite values ​​{{0, 0}, {9.5531391950081541e + 99, inf}} passed to [NSThemeFrame initWithFrame :]
Terminated: 15

If you know the solution, please let me know.

@tanguband tanguband added the bug Something isn't working label Aug 19, 2021
@backwardsEric
Copy link
Owner

Given that it works in one account and not another, I would suspect something has gone wrong with the stored preferences in ~/Library/jp.osdn.hengband.plist . You can get a human-readable version of those from the command line by running this in a Terminal (which puts the output in ~/Desktop/hengband-settings.txt):

defaults read ~/Library/Preferences/jp.osdn.hengband.plist > ~/Desktop/hengband-settings.txt

Could you post what those settings are for the account that has trouble running hengband?

You can clear out the settings by running this in a Terminal:

defaults delete ~/Library/Preferences/jp.osdn.hengband.plist

That may resolve your immediate problem.

@tanguband
Copy link
Author

Thank you for suggesting a solution

After deleting the plist, it started up safely

For reference, I will attach the plist before deletion

I hope it will help you in future development.

hengband-settings.txt

@tanguband
Copy link
Author

additional information

I used to manually delete "plist" using "Finder".

After checking, it seems that it will not disappear completely unless it is deleted with the "defaults delete" command.

This seems to be the cause.

@backwardsEric
Copy link
Owner

In the account where Hengband worked, were you using the RictyDiminished-Bold font for the subwindows as well or were you using something else? Had something changed about that font (uninstalled, reinstalled, ...) around the time Hengband started having trouble?

backwardsEric added a commit that referenced this issue Aug 20, 2021
…e. Likely resolves the underlying problem in #19 .
@backwardsEric
Copy link
Owner

With a font specified in the preferences that wasn't available on the system, I got similar symptoms to what you reported. The changes in 69beaff should make the front-end for Hengband 3 more robust in that case. I'll port those changes to the front ends for 2.2.1 and 1.6.2 as well.

backwardsEric added a commit that referenced this issue Aug 20, 2021
…e. Likely resolves the underlying problem in #19 .
backwardsEric added a commit that referenced this issue Aug 20, 2021
…. Likely resolves the underlying problem in #19 .
backwardsEric added a commit to backwardsEric/angband that referenced this issue Aug 20, 2021
…vailable. backwardsEric/hengband#19 is an example (with Hengband's macOS front end) of the symptoms that are avoided.
backwardsEric added a commit to backwardsEric/sil-q that referenced this issue Aug 20, 2021
…vailable. backwardsEric/hengband#19 is an example (with Hengband's macOS front end) of the symptoms that are avoided.
sil-quirk pushed a commit to sil-quirk/sil-q that referenced this issue Aug 20, 2021
…vailable. backwardsEric/hengband#19 is an example (with Hengband's macOS front end) of the symptoms that are avoided. (#84)
NickMcConnell pushed a commit to angband/angband that referenced this issue Aug 20, 2021
…vailable. backwardsEric/hengband#19 is an example (with Hengband's macOS front end) of the symptoms that are avoided.
NickMcConnell pushed a commit to NickMcConnell/FAangband that referenced this issue Aug 20, 2021
…vailable. backwardsEric/hengband#19 is an example (with Hengband's macOS front end) of the symptoms that are avoided.
@tanguband
Copy link
Author

The font remained standard in the other account that was started.
Ricty Diminished-Bold font was decommissioned in Font Book for accounts that didn't start.
It seems that the cause has been clarified.
Thank you for the solution.

@backwardsEric
Copy link
Owner

The changes for 1.6.2 and 2.2.1 have been released so I'll close this.

msearle5 pushed a commit to msearle5/xygos that referenced this issue Aug 31, 2021
…vailable. backwardsEric/hengband#19 is an example (with Hengband's macOS front end) of the symptoms that are avoided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants