Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Crash in QWindowsKeyMapper::possibleKeys

Crash in QWindowsKeyMapper::possibleKeys

Scheduled Pinned Locked Moved Solved General and Desktop
5 Posts 2 Posters 896 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Thuan_FirelightT Offline
    Thuan_FirelightT Offline
    Thuan_Firelight
    wrote on last edited by
    #1

    I have been encountering an intermittent crash in QWindowsKeyMapper::possibleKeys and it seems like the nativeVirtualKey() in the QKeyEvent is > 255. The value I am seeing (based on a minidump) is 9827. Not entirely sure how it got into that state. Has anyone experience a similar crash before?

    There is this bug report https://bugreports.qt.io/browse/QTBUG-36061 but judging from the comments, Qt doesn't appear too keen to put in a simple fix to early out if the nativeVirtualKey() causes an array out of bound.

    Anyone has any thoughts as to why the virtual key would be greater than 255?

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi and welcome to devnet,

      No real thoughts about it be in any case there's a fix submitted for Qt 5 that should solve this.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      Thuan_FirelightT 1 Reply Last reply
      0
      • SGaistS SGaist

        Hi and welcome to devnet,

        No real thoughts about it be in any case there's a fix submitted for Qt 5 that should solve this.

        Thuan_FirelightT Offline
        Thuan_FirelightT Offline
        Thuan_Firelight
        wrote on last edited by Thuan_Firelight
        #3

        @SGaist

        Hi, mind if I ask which version of Qt 5 the fix was submitted for? I am using Qt 5.4.1 and still getting the problem. Forgot to mention this in my opening post.

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #4

          No I don't :) For 5.6, it's pending integration.

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          1 Reply Last reply
          1
          • Thuan_FirelightT Offline
            Thuan_FirelightT Offline
            Thuan_Firelight
            wrote on last edited by
            #5

            Thanks. We might consider just integrating the change (a simple early out) into our 5.4.1 since upgrading Qt version is more involved.

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved