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 process was ended forcefully.
Qt 6.11 is out! See what's new in the release blog

The process was ended forcefully.

Scheduled Pinned Locked Moved Solved General and Desktop
17 Posts 3 Posters 16.0k 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.
  • DiracsbracketD Diracsbracket

    @Limer
    I downloaded your project and had the same error as you have, immediately upon running the program, without any debug info provided.

    I'm using VS2017 Community on Windows 10, and found a post on this forum related to CDB problems like this (immediately after starting a program and no further debug info given) where it was suggested that this was caused by a Windows Update. So, I tried to repair my VS2017 installation using the installer, and sure enough, some updates seemed to be pending (the VS installer prompted directly for it to be updated first). The "Repair" hanged on Microsoft.VisualCcp.Redist.14, so I killed the repair rebooted the computer. Lo and behold, there were some Win10 updates pending too it seems.

    After relaunching the VS Installer, I was prompted this time for a VS2017 update instead.
    After installing that update, your program ran fine (I use the x64 libraries of Pylon).

    0_1521521150817_7cdb5fef-ce16-4c57-9ad9-427c6d10b700-image.png

    So, try to update your VS installation (assuming you use VS) and check if your system has some Windows Updates pending (in which case you should reboot to install them).

    LimerL Offline
    LimerL Offline
    Limer
    wrote on last edited by
    #8

    @Diracsbracket Sorry, I update the windows(and restart pc several times), and update visual studio 2017 community to 15.6.3,but it doesn't work......sad.....

    DiracsbracketD A 2 Replies Last reply
    0
    • LimerL Limer

      @Diracsbracket Sorry, I update the windows(and restart pc several times), and update visual studio 2017 community to 15.6.3,but it doesn't work......sad.....

      DiracsbracketD Offline
      DiracsbracketD Offline
      Diracsbracket
      wrote on last edited by Diracsbracket
      #9

      @Limer
      I never used the Pylon before, so I also installed the latest version of it today in order to try out your program. Maybe also update Pylon and use the new .lib files of it in your Qt project? Also, I used the x64 version, but that's probably not an issue. The Qt version I tried it with is Qt 5.10.0.

      LimerL 1 Reply Last reply
      0
      • LimerL Limer

        @Diracsbracket Sorry, I update the windows(and restart pc several times), and update visual studio 2017 community to 15.6.3,but it doesn't work......sad.....

        A Offline
        A Offline
        ambershark
        wrote on last edited by
        #10

        @Limer I wonder if it's mixing dlls from somewhere on your system?

        You could try using listdlls from sysinternals to see what dlls your application is using. Or try isolating it by running in a cmd with your path environment empty and copying in just the dlls you know you would need for your app.

        My L-GPL'd C++ Logger github.com/ambershark-mike/sharklog

        LimerL 1 Reply Last reply
        1
        • DiracsbracketD Diracsbracket

          @Limer
          I never used the Pylon before, so I also installed the latest version of it today in order to try out your program. Maybe also update Pylon and use the new .lib files of it in your Qt project? Also, I used the x64 version, but that's probably not an issue. The Qt version I tried it with is Qt 5.10.0.

          LimerL Offline
          LimerL Offline
          Limer
          wrote on last edited by
          #11

          @Diracsbracket My project has the newest pylon , I download it on 2018/03/19.

          0_1521526032161_捕获.PNG

          1 Reply Last reply
          0
          • A ambershark

            @Limer I wonder if it's mixing dlls from somewhere on your system?

            You could try using listdlls from sysinternals to see what dlls your application is using. Or try isolating it by running in a cmd with your path environment empty and copying in just the dlls you know you would need for your app.

            LimerL Offline
            LimerL Offline
            Limer
            wrote on last edited by
            #12

            @ambershark I tried my company computer(windows 7), and it success...........................................I think it's my own pc windows10's problem.........I don't know what the problem is, and I'm afraid there will be other strange mistakes in the future. At least I can go on working now.(I want to reinstall my own pc now.............)

            A DiracsbracketD 3 Replies Last reply
            0
            • LimerL Limer

              @ambershark I tried my company computer(windows 7), and it success...........................................I think it's my own pc windows10's problem.........I don't know what the problem is, and I'm afraid there will be other strange mistakes in the future. At least I can go on working now.(I want to reinstall my own pc now.............)

              A Offline
              A Offline
              ambershark
              wrote on last edited by
              #13

              @Limer You don't need to reinstall everything. It's just a bad dll hiding somewhere.

              Use process explorer:
              https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

              or listdlls:
              https://docs.microsoft.com/en-us/sysinternals/downloads/listdlls

              And find out where the bad dll is. Then fix that issue and you should be back to normal on your win10 computer.

              Or just be cool like me and switch to linux. ;)

              My L-GPL'd C++ Logger github.com/ambershark-mike/sharklog

              LimerL 1 Reply Last reply
              1
              • LimerL Limer

                @ambershark I tried my company computer(windows 7), and it success...........................................I think it's my own pc windows10's problem.........I don't know what the problem is, and I'm afraid there will be other strange mistakes in the future. At least I can go on working now.(I want to reinstall my own pc now.............)

                DiracsbracketD Offline
                DiracsbracketD Offline
                Diracsbracket
                wrote on last edited by
                #14

                @Limer
                Too bad. The strange thing is that is worked on your Win10 PC at first...
                In any case, good luck!

                1 Reply Last reply
                0
                • A ambershark

                  @Limer You don't need to reinstall everything. It's just a bad dll hiding somewhere.

                  Use process explorer:
                  https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

                  or listdlls:
                  https://docs.microsoft.com/en-us/sysinternals/downloads/listdlls

                  And find out where the bad dll is. Then fix that issue and you should be back to normal on your win10 computer.

                  Or just be cool like me and switch to linux. ;)

                  LimerL Offline
                  LimerL Offline
                  Limer
                  wrote on last edited by
                  #15

                  @ambershark Thank you for your help.

                  And, if there is Visual Studio Linux vertion in the future, I will definitely switch to linux. HaHaHa................

                  A 1 Reply Last reply
                  1
                  • LimerL Limer

                    @ambershark I tried my company computer(windows 7), and it success...........................................I think it's my own pc windows10's problem.........I don't know what the problem is, and I'm afraid there will be other strange mistakes in the future. At least I can go on working now.(I want to reinstall my own pc now.............)

                    DiracsbracketD Offline
                    DiracsbracketD Offline
                    Diracsbracket
                    wrote on last edited by Diracsbracket
                    #16

                    @Limer said in The process was ended forcefully.:

                    I think it's my own pc windows10's problem

                    I also noticed that you also have the 64bit Qt kit installed for VS2017. Could you give it one last try and build the 64bit version of your program (also edit the library path in your .pro file to x64)?

                    1 Reply Last reply
                    0
                    • LimerL Limer

                      @ambershark Thank you for your help.

                      And, if there is Visual Studio Linux vertion in the future, I will definitely switch to linux. HaHaHa................

                      A Offline
                      A Offline
                      ambershark
                      wrote on last edited by
                      #17

                      @Limer Lol best you'll get from MS in linux is visual studio code... which is nothing like visual studio. :)

                      You can always use something really cool like clion from jetbrains though. It's a great IDE.

                      My L-GPL'd C++ Logger github.com/ambershark-mike/sharklog

                      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