ltchiptool gui install on macos

[pauloshendriks]

I am looking for some help with getting lichiptool running
The installation of itchiptool seems to go alright but when I want to start the gui with "itchiptool gui" it crashes with the following errors.

zsh: segmentation fault ltchiptool gui
/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/multiprocessing/resource_tracker.py:254: UserWarning: resource_tracker: There appear to be 4 leaked semaphore objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d '

can you help me with this error?

the other warning I get is

what does this mean W: /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/ltctplugin/esphomeota/gui.py:8: UserWarning: ltchiptool.gui.base.zc is deprecated, migrate to ltchiptool.gui.mixin.zc
from ltchiptool.gui.base.zc import ZeroconfBase

the cli seems to work

any help would be very much appreciated

PS I consulted chatGPT for troubleshooting, however several of the hint I would not know how to perform.
for reference this is what I got:

+++++++++++++++

Check Python Version Compatibility: Ensure that the version of ltchiptool you are using is compatible with Python 3.12. Some tools and libraries may not be fully compatible with the latest Python versions.
Update ltchiptool and Dependencies: Make sure you are using the latest version of ltchiptool and its dependencies. Updating to the latest releases might include fixes for issues related to Python versions and GIL management.
Review Multiprocessing Code: If you have control over the Python code that uses multiprocessing, review it to make sure you are correctly handling shared resources, locks, and releasing the Global Interpreter Lock when needed. It's important to manage the GIL properly, especially in a multiprocessing environment.
Check for Known Issues: Check the documentation, release notes, or issue tracker for ltchiptool to see if there are any known issues or workarounds related to the error you're encountering.
Resource Cleanup: Address the warning about leaked semaphore objects mentioned in the resource_tracker warning. Make sure you are properly cleaning up resources, especially in a multiprocessing scenario, to avoid unexpected behavior.
Debugging: If the issue persists, you may need to use debugging tools to identify the source of the problem. Running the application within a debugger (such as gdb for CPython) can help you trace the issue back to its origin.
Consult Documentation and Community: Check the official documentation for ltchiptool and related libraries. If there's a community or forum associated with the tool, consider seeking help or reporting the issue to the community.