Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Update: Forum Guidelines & Code of Conduct


    Qt World Summit: Early-Bird Tickets

    Solved FTH 1480 issue

    General and Desktop
    2
    4
    1954
    Loading More Posts
    • 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.
    • Cobra91151
      Cobra91151 last edited by

      Hi! I get *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. *** message when running my application. How to fix this issue? Thanks.

      1 Reply Last reply Reply Quote 0
      • mrjj
        mrjj Lifetime Qt Champion last edited by mrjj

        Hi
        When does it happen ?

        Its a windows thing and can be disabled with
        HKEY_LOCAL_MACHINE\Software\Microsoft\FTH\Enabled ( full system)
        or for an single app
        https://stackoverflow.com/questions/5020418/how-do-i-turn-off-the-fault-tolerant-heap

        but normally it will go away if you completely clean the build folder and rebuild

        However, if it happens when deployed, its another matter.

        Cobra91151 1 Reply Last reply Reply Quote 2
        • Cobra91151
          Cobra91151 @mrjj last edited by

          @mrjj

          The issue was when launching application in release mode. I have tested it and it crashes few times but I have fixed the crashes and the *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. *** message appeared. But now it has been fixed.

          I have deleted: Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers\your_application.exe entry.

          Thanks.

          mrjj 1 Reply Last reply Reply Quote 0
          • mrjj
            mrjj Lifetime Qt Champion @Cobra91151 last edited by

            @Cobra91151
            Ok super. So it just had a record and hence showed the warning even after the app
            stopped crashing.
            Good you found the reason for the crash.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post