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

madvise() terminates application due to EBADF code

    XMLWordPrintable

Details

    • Linux/Other display system
    • 2dc0fc1a1b (qt/qtdeclarative/6.4) 2034e10c93 (qt/qtdeclarative/dev) 2034e10c93 (qt/qtdeclarative/wip/material3) 2dc0fc1a1b (qt/tqtc-qtdeclarative/6.4) 2034e10c93 (qt/tqtc-qtdeclarative/dev)

    Description

      After QTBUG-100431 the application crashes if the call

      madvise(address, bytes, MADV_WILLNEED)

      returned an EBADF error.

      There is no swap on our systems. I assume that in such conditions there is no need to terminate the application on an EBADF error.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-106269 Qt Quick apps immediately crash under Android 6

          • 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; 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

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-106864 Reg-5.15.9->5.15.10: Android crash on startup on armv7 (32bit) devices

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              ulherman Ulf Hermann
              maksimshapovalov Maksim Shapovalov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: