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. The program has unexpectedly finished with code 1073741819
Forum Updated to NodeBB v4.3 + New Features

The program has unexpectedly finished with code 1073741819

Scheduled Pinned Locked Moved General and Desktop
8 Posts 4 Posters 2.7k Views 1 Watching
  • 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.
  • H Offline
    H Offline
    holygirl
    wrote on last edited by
    #1

    I have read many threads regarding the program crashing with code 1073741819 but in most cases it's the pointer or memory allocation problem. My application was running smoothly. I made no changes and when I randomly ran the application, this error was thrown. I read many threads on how to solve it but it didn't help. Reopening Qt solved it. Today I have the same problem again. I tried restarting Qt but the problem persists.

    PLEASE HELP!

    I don't know how to setup a debugger or even install one. And I can't post my code because I have more than 8 classes and the code is huge.

    1 Reply Last reply
    0
    • Q Offline
      Q Offline
      qxoz
      wrote on last edited by
      #2

      Yes you are rigth, this is a allocation problem. When i get same error debugging helps me and every time it was a buggy code. What toolchain you use? Why cant debug it? Any way you can put qDebug() messages into a suspicious parts of the code.

      1 Reply Last reply
      0
      • H Offline
        H Offline
        holygirl
        wrote on last edited by
        #3

        That's the thing. The application works well. No issues, no errors. Suddenly it starts throwing this error so I have NO idea which part of the code is buggy.
        Btw, an hour after I posted the question, my app started working. It's mysterious. But I want to be prepared for the next time it behaves unexpectedly

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

          If you can't debug, you have to check that every allocation is associated with a deallocation (That can be partially done using a static code analyzer).

          If you're on linux/os x (but the error code makes me think you're running Windows) you might want to run your application through Valgrind.

          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
          0
          • H Offline
            H Offline
            holygirl
            wrote on last edited by
            #5

            The application is running fine for now. I'll give Valgrind a shot and mark this question solved if it works out for me.

            Thanks for your reply.

            EDIT: I'm working on Windows and I just realized Valgrind is for Linux. I'll look for an alternative

            1 Reply Last reply
            0
            • U Offline
              U Offline
              utcenter
              wrote on last edited by
              #6

              http://www.drmemory.org/

              1 Reply Last reply
              0
              • Q Offline
                Q Offline
                qxoz
                wrote on last edited by
                #7

                utcenter@ Nice app

                how can i locate problem from this message?:

                Error #10: LEAK 264 direct bytes 0x025bd510-0x025bd618 + 0 indirect bytes

                0 ole32.dll!CoRevokeInitializeSpy +0x1a7 (0x760b8362 <ole32.dll+0x48362>)

                1 ole32.dll!CoRevokeInitializeSpy +0x20b (0x760b83c6 <ole32.dll+0x483c6>)

                2 ole32.dll!CoRevokeInitializeSpy +0x34f (0x760b850a <ole32.dll+0x4850a>)

                3 ole32.dll!CoGetTreatAsClass +0x2339 (0x7609c801 <ole32.dll+0x2c801>)

                4 KERNEL32.dll!BaseThreadInitThunk +0x11 (0x74f13677 <KERNEL32.dll+0x13677>)

                5 ntdll.dll!RtlInitializeExceptionChain +0x62 (0x76ff9d72 <ntdll.dll+0x39d72>)

                6 ntdll.dll!RtlInitializeExceptionChain +0x35 (0x76ff9d45 <ntdll.dll+0x39d45>)

                1 Reply Last reply
                0
                • U Offline
                  U Offline
                  utcenter
                  wrote on last edited by
                  #8

                  I haven't used it myself, just shared it since it runs on windows as well.

                  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