Linux build qt.glx problem

[SGaist]

Hi,

What Linux distribution are you using ?
Are you doing anything OpenGL in your application ?

[Bremenpl]

@SGaist Hi,
I am using Ubuntu 18.04. I am not using opengl in the code.

[SGaist]

What graphic stack do you have on your machine ?

[Bremenpl]

@SGaist I am using a virtualized system (virtualbox).

[SGaist]

So a virtualbox running Ubuntu 18.04 ?
Did you activate 3D acceleration ?
What is your host OS ?

[Bremenpl]

@SGaist yes, 3D acceleration is on. My host is windows 10.

[SGaist]

Wait, it's on your Linux that it is failing. What graphics card do you have ?

[Bremenpl]

@SGaist 2 graphics cards: intel integrated (the one that comes with i7-8750H) and Radeon Pro WX 7100. I think VB uses the second one, will doublecl check tommorow.

[Bremenpl]

@SGaist Hi, I have noticed that when I turn off 3d acceleration in the VM, the messages dispensary, but the app crashes as before on shutdown...

[jars121]

Any chance you were able to resolve this @Bremenpl ? I've got exactly the same issue under exactly the same circumstances (Ubuntu 18.04 under VirtualBox in Windows 10, running Qt 5.12.3).

[Bremenpl]

@jars121 unfortunetally not. I am still dealing with this bug in qt 5.13 (android build also crashes).

[SGaist]

Can you post the stack trace of the crash ?

[Bremenpl]

@sgaist Hi, sorry for late answer- do you mean a screenshot from the call stack in debug view?

Ps: mac os build crashes the same way, havent tested only ios build yet.

[Bremenpl]

@sgaist Here is the call stack along with the segfault moment in code (VB Ubuntu 18.04 x64):

Seems like the problem lies somewhere within the Qt OPCUA code.

[SGaist]

Do you have the same stack trace on macOS ?

[Bremenpl]

@sgaist Its pretty much the same I think:

Screen Shot 2019-08-22 at 11.10.40

[SGaist]

Can you test again with the latest Qt 5.13 ?
There's also going to be a release of Qt 5.12.5 if not already.

[Bremenpl]

@sgaist Hi, just FYI- yje iOS build works without problems, like Windows build (exits with code 0).
I am currently using 5.13.0. Did you mean to update to the latest 5.13.2?