CheryTree .99.56 Keeps Crashing/Closing on Windows

[Patuba13]

Version, Operative system
Cherry Tree .99.56 Windows 10 Build 10.0.19045

Describe the bug
I have been using CherryTree 0.99.56 for about 2 weeks without issue. I only have 1 data file I am working on. When I try to create a new child node to my existing data file, CherryTree just closes out. I have tried making a new instance and that automatically closes CherryTree. I have uninstalled and re-installed CherryTree with no luck. I am able to download and use CherryTree 0.39.4 for the time being.

Not sure if you can reproduce but I have attached my data file in case you need it.

Cherry_Notes.zip

[Sisyfos3]

@giuspen ,I experience the same thing, running 0.99.56 flatpak version on Linux Mint Mate 21.1. Attempting to create a new node or subnode immediately closes Cherrytree. Noticed this today.
However, on my work computer, Windows 10 Enterprise 22H2, everything works as expected.

Downloaded the "regular" version, updated through the ppa, and it works fine under Linux.
/Sisyfos3

[demijohn]

I have the same problem as @Sisyfos3, running 0.99.56 snap version on Ubuntu 22.04.2 LTS. Creating new node (or edit properties of existing node) closes CherryTree with this message in command line:
[2023-07-11 12:02:00.735] [gtk] [info] unhandled exception (type std::exception) in signal handler: what: basic_string::_M_construct null not valid

[giuspen]

I'll try and reproduce shortly and update here

[giuspen]

It would help me to have the config file exported and attached to the ticket. File-->Preferences-->Export Preferences

[demijohn]

It would help me to have the config file exported and attached to the ticket. File-->Preferences-->Export Preferences

My config:
config_2023.07.12_09.09.37.zip

[giuspen]

Many thanks @demijohn I can confirm that this bug is fixed with yesterday's commit. I will release a new version in the next few days.

[giuspen]

NOTE: an immediate workaround is to remove in config.cfg, while cherrytree is not running, the line last_icon_sel=0 - in fact doing that and confirming that then cherrytree is not crashing anymore will be a further confirmation (cherrytree should regenerate that in the subsequent session with the default value last_icon_sel=132).

Honestly I haven't understood yet what caused that value to go zero so it can happen again but at least that will be harmless since the next version.

[giuspen]

UPDATE: I managed to understand what caused last_icon_sel=0 should not happen anymore in new version

[demijohn]

I can confirm workaround is working. Thanks @giuspen for fast solution.

[Patuba13]

@giuspen That fixed it on the Windows version as well, thank you very much!

I've noticed I have a lot of .Cherry_Notes x.ctb~~~ files in my CherryTree folder. With X being a different number, are those normal?

[giuspen]

@Patuba13 the backup files should be .filename~ while those with the number should be only temporary, so no it's not expected. Such thing may have happened because of the crashes though. Can you remove all unexpected files and monitor if that appears again after you save?