-
Notifications
You must be signed in to change notification settings - Fork 34
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
The viewer crashes when tidying up the texture cache #75
base: master
Are you sure you want to change the base?
Conversation
Probably because openGL has already done it by the time the viewer tries it. After all it's just a cache and there shouldn't be any reason to clear it manually? https://doc.qt.io/qt-5.15/qglcontext.html#deleteTexture
cmake needs to be told which openGL version is used. The cmake file in the python wrapper is not explicitely targeting python version 3. Changed the commands to the new cmake 3 ones.
The cmake files for the python wrappers are a bit out of date and are not detecting python3 explicitly. The commands to find python are deprecated as they do not force python3. I've changed that python3 is searched and also installed in the architecture dependent python dirs. Also squelched a cmake openCV warning. |
Thanks for the PR. The documentation of |
Indeed. It segfaults in the destructor. By that time it seemed to have been already tidied up. I've got just a bog standard ubuntu LTS and segfaults there. It's certainly only caused by one of the pre-defined robots and not all which is even stranger. |
We could try to run it in |
I put the "deleteTexure" back in.
...and it crashes again. |
Probably because openGL has already done it by the
time the viewer tries it. After all it's just a cache
and there shouldn't be any reason to clear it manually?
https://doc.qt.io/qt-5.15/qglcontext.html#deleteTexture
How to reproduce it? Compile the line follower here:
https://github.com/glasgowneuro/feedforward_closedloop_learning/tree/master/linefollower
As you can see it's not using any of the 3 pre-defined robots but creates its own robot. So only realised that the 3 default robots are always loaded. That seems to be ok. The texture IDs look legit. It's just during the tidying up it happens.