Open tlpss opened 1 year ago
Thanks for the report. Seems like threads may still be busy when the add-on is unregistered, and then properties that the threads expect are no longer available. Will investigate soon, though I have not heard any similar reports nor have I ever run into this issue in normal usage, so this is not the top priority at the moment.
Describe the bug
When using the add-on, blender does not close when pressing CTRL+Q. It does close when pressing CTLR+Q (or pressing the UI button) and then pressing CTRL+C in the terminal, after which a thread appears that seems to suggest it was stuck in acquiring a lock.
This does not happen deterministically, sometimes blender closes by itself.
When disabling the add-on, the issue goes away.
Console log
CTRL+Q in UI + CTRL+C in terminal:
CTRL+Q in UI:
To Reproduce run
blender
from the terminal, then try to close.Expected behavior blender closes as expected on CTRL+Q in the UI.
Additional context blender version: 3.4.1 add-on version: 1.1.5