Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-65225

StackView segmentation fault crash

    XMLWordPrintable

Details

    • Bug
    • Resolution: Incomplete
    • P1: Critical
    • None
    • 5.9.3, 5.12.0
    • Quick: Controls 2
    • None
    • Android 4.4.4, Android 5.1
      Ubuntu 18.10

    Description

      Run example attached and start click button, it will load and unload the MainPage that contain navigationbar (ListView) and StackView where the root Item always will be replaced by the Item selected from navigationbar.
      MainPage implements concept from ekkescorner's Drawer Navigation App (https://appbus.wordpress.com/2016/06/20/drawer-navigation-app/)

      It will crash soon or later.
      Also switching between menus in navigationbar (Item1 ... Item4) leads to crashes.

      It crash randomly usually without any debug messages, but sometimes I saw this:

      F/libc    ( 6530): invalid address or address of corrupt block 0x7c7df468 passed to dlfree
F/libc    ( 6530): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 6585 (Thread (pooled))

      or this:

      F/libc    (16328): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 16422 (Qt3DCore::QAspe)

      There is the Scene3D in application. I did try without it but app crashed once. Without Scene3D it hard to crash app, one needs to furiously tap on buttons.

      I've never got crash on desktop (Windows 7).

      Attachments

        1. backtrace1.txt
          26 kB
          Oleg
        2. backtrace2.txt
          31 kB
          Oleg
        3. backtrace3.txt
          31 kB
          Oleg
        4. crash_with_loaders.zip
          3.54 MB
          Oleg
        5. crash_with_stack.zip
          3.54 MB
          Oleg
        6. StackView Segfault.txt
          2 kB
          Peter Würtz

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-65169 Crash when using connect() (presumably from dynamic created item in a Loader)

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; Flaky tests; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              seanharmer Sean Harmer
              lukegluke Oleg
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes