Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. App crashed with ..QV4::Value::FromHeapObject
Forum Updated to NodeBB v4.3 + New Features

App crashed with ..QV4::Value::FromHeapObject

Scheduled Pinned Locked Moved Unsolved QML and Qt Quick
5 Posts 3 Posters 474 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.
  • SheepS Offline
    SheepS Offline
    Sheep
    wrote on last edited by
    #1

    Greetings am trying to develop an app with qml..but it keeps crashing with the debugger pointing to that...Is it my code ...or some qt error. Am using Qt 6.5 msvc 2019 win10.qtcreator_2kUUKpbrhh.png

    1 Reply Last reply
    0
    • A Offline
      A Offline
      aran
      wrote on last edited by
      #2

      It'll be hard to help without seeing the code itself...

      SheepS 1 Reply Last reply
      0
      • A aran

        It'll be hard to help without seeing the code itself...

        SheepS Offline
        SheepS Offline
        Sheep
        wrote on last edited by
        #3

        @aran Thanks for the reply..the problem is the projets is so big..~1000 qml files...and i also cant`t trace the real cause of the issue, perhap some clue on whats the use of QV4::value:fromHeapObject then i can try to trace it.

        A 1 Reply Last reply
        0
        • SheepS Sheep

          @aran Thanks for the reply..the problem is the projets is so big..~1000 qml files...and i also cant`t trace the real cause of the issue, perhap some clue on whats the use of QV4::value:fromHeapObject then i can try to trace it.

          A Offline
          A Offline
          aran
          wrote on last edited by aran
          #4

          @Sheep The problem is that the error message is not very helpful. It crashes when reading some value from the heap somewhere. If you can track down where/when it crashes (maybe with some debug statements), that might help isolate the guilty part of the code.

          Also, there is something about if and setTimeOut in the panel on the right, maybe checking the contents of these could provide some clue.

          mranger90M 1 Reply Last reply
          0
          • A aran

            @Sheep The problem is that the error message is not very helpful. It crashes when reading some value from the heap somewhere. If you can track down where/when it crashes (maybe with some debug statements), that might help isolate the guilty part of the code.

            Also, there is something about if and setTimeOut in the panel on the right, maybe checking the contents of these could provide some clue.

            mranger90M Offline
            mranger90M Offline
            mranger90
            wrote on last edited by
            #5

            @aran I've recently run into this and can't seem to find an answer.
            The crash happens on the application exit. For most situations this probably wouldn't be an issue but we have a monitor looking for the exit code, and the crash prevents that from happening.
            I'm in a similar situation with dozens of qml files and models so debugging is difficult. The call stack is no help because it looks a lot like yours. A previous release (based on Qt 5.12.4) worked without the crash but the new one (based on 5.15.8) crashes. There have been other modifications so I'm reluctant to point at the Qt version at this time.

            I'm wondering if you've had any luck with solving this issue.

            Thanks.

            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