-
Notifications
You must be signed in to change notification settings - Fork 25
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
Not freed memory blocks on blender close #47
Comments
a default qdialog however doesn't do this when run in the blender terminal: import PySide2
import PySide2.QtWidgets
import PySide2.QtWidgets as w
d = w.QDialog()
d.show() |
closing blender after running the following cause an acces violation exception import PySide2
import PySide2.QtWidgets
import PySide2.QtWidgets as w
from PySide2.QtWidgets import QApplication
app = QApplication.instance()
bw = app.blender_widget
#d = w.QDialog() # this is fine
d = w.QDialog(bw) # acces violation on exit
d.show()
# close blender now without closing the widget |
We had something like
on blender close with PySide2 |
Great to hear pyside6 fixed this AFAIK this exception with pyside 2 doesnt cause issues since it only happens on closing blender, after executing any scripts hooked to exit. Qt does mention any wrapping of a non qt window in a qt window is possible but not officially supported. So bugs like these are possible |
this bug prevented qt from saving the window position and size to restore in the next session. |
weirdly enough this still happens when bqt is set to no wrap mode, investigate. ... |
|
after mergin in PR #44 to fix the access violation exception,
the following error happens on quiting blender, but only if a qt window was launched in blender
Error: Not freed memory blocks: 4, total unfreed memory 0.000351 MB
Originally posted by @hannesdelbeke in #44 (comment)
The text was updated successfully, but these errors were encountered: