-
Notifications
You must be signed in to change notification settings - Fork 189
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
QML engine GCs resources after receiving reference #68
Comments
Panicing variant when trying to use the return value of
Output:
|
The problem is the same described in this thread: https://groups.google.com/d/msg/go-qml/h5gDOjyE8Yc/jyG9Pia2GaMJ As explained there, the QML engine is destroying the old proxy object even though it was just handed a reference to it, which seems like bug, but I won't argue about that nor expect it to be timely fixed. Instead, I'm planning to simplify significantly the reference handling logic by making Go own all the values, and use its garbage collector to release resources on the QML side. I'll keep you posted via this ticket. |
Got it, thanks, I'll keep my eyes and ears open :) |
Sorry it's taking a while to get to this. I'll move it up in the agenda and will go back to it after the new gl package structure is working. |
I'm back into this. Should have a fix shortly. |
Okay, rather than changing too much right now, I'm going for a more conservative approach which I should have implemented long ago. |
Excellent! Appears to work fine from very minor testing, thanks! :) |
Try running this test:
I'm receiving a long about 3 seconds worth of the expected output and then all of a sudden:
If I don't fail immediately, it'll output the correct data again for a bit until it fails the next time.
Occurs in both v0 and v1
The text was updated successfully, but these errors were encountered: