Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

crashing after relayout



  • My Qt app is crashing when I rotate the screen position from portrait to landscape mode. It didn't have a problem with this before today, so I'm suspicious that my update to Qt 5.11 may be related.

    Here is the debug log leading up to the crash:

    D SurfaceView: Relayout returned: oldFrame=[0,63][1080,1920] newFrame=[0,63][1080,1920] result=0x1 surface={Surface(name=null)/@0x48adc8a isValid=true -789594112}
    D ViewRootImpl@18e88da[QtActivity]: MSG_RESIZED_REPORT: ci=Rect(0, 63 - 0, 0) vi=Rect(0, 63 - 0, 0) or=2
    D ViewRootImpl@18e88da[QtActivity]: Relayout returned: oldFrame=[0,0][1920,1080] newFrame=[0,0][1920,1080] result=0x21 surface={isValid=true -462499840} surfaceGenerationChanged=false
    D mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000,  [1920x1080]-format:1
    D ViewRootImpl@18e88da[QtActivity]: mHardwareRenderer.updateSurface() mSurface={isValid=true -462499840}
    F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xf in tid 17846 (qtMainLoopThrea)
    D SurfaceView: Relayout returned: oldFrame=[0,63][1080,1920] newFrame=[0,63][1920,1080] result=0x21 surface={Surface(name=null)/@0x48adc8a isValid=true -789598208}
    
    
    "myapp" died.
    

    Any suggestions?



  • @kgregory
    Can you post a minimal example that produces that behavior?



  • I wish I could tell what the problem is. My app is far from minimal. I re-installed the previous version of QT where I know this problem didn't occur and that didn't solve it. So it must be something I changed, I just can't figure out what.

    I also found that it is OK with whichever screen orientation it starts up in, it just crashes when I flip the orientation.

    If I were able to get to a minimal example that produces this behavior, then I think I'd have solved my problem.

    I wonder if It's just got too many objects to re-size and it crashes from the workload?


Log in to reply