Forum

    • Register
    • Login
    • Search
    • Categories

    Still getting heap space problems

    General Questions
    5
    7
    210
    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.
    • Lindon
      Lindon last edited by

      So I've set the compiler option /bigobj but that doesn't seem to fix the out of heap space fatal error on Visual Studio, 50% of the time it fails with this - I can sort-of help things along by rebooting my machine and immediately running HISE (so nothing else running at all) but its worrying...

      Any one else having this problem? Anyone got any additional suggestions?

      HISE Development for hire.
      www.channelrobot.com

      orange 1 Reply Last reply Reply Quote 0
      • orange
        orange @Lindon last edited by

        @Lindon maximum file size of the embedded files has a limitation of 50 mb. Are you using big images?

        develop Branch / XCode 13.1
        macOS Monterey / M1 Max

        Lindon 1 Reply Last reply Reply Quote 0
        • Lindon
          Lindon @orange last edited by

          @orange - nope - std images , plus a limited number of IRs (sometimes none), and no loop audio...

          HISE Development for hire.
          www.channelrobot.com

          Natan 1 Reply Last reply Reply Quote 0
          • Natan
            Natan @Lindon last edited by Natan

            @Lindon Lindon
            Check The Font Size, ( If You have Custom Ones)
            I Faced with the same Issue Last week, With an almost Empty Project.
            And found out the Fonts Were Too big, Like 6 M.b And 10 styles. So Easily Jumped into The 90 M.b In Dll Size.

            1 Reply Last reply Reply Quote 0
            • Dan Korneff
              Dan Korneff last edited by

              I just ran into this when opening older projects on my new rig. Images and binary are way below 50mb.
              Did a little searching and found that this may happen if Visual Studio doesn't use the 64 bit toolset. I think it's some kind of global change between VS2017 and 2019.
              Manually setting the architecture in Environmental Variables fixed the problem for me.
              https://phoenixnap.com/kb/windows-set-environment-variable

              HEAPSPACE.png

              Dan Korneff - Producer / Mixer / Audio Nerd

              Christoph Hart 1 Reply Last reply Reply Quote 6
              • Christoph Hart
                Christoph Hart @Dan Korneff last edited by

                @dustbro HERO!!!

                Dan Korneff 1 Reply Last reply Reply Quote 0
                • Dan Korneff
                  Dan Korneff @Christoph Hart last edited by

                  @christoph-hart Glad I could finally help YOU for once 😁

                  Dan Korneff - Producer / Mixer / Audio Nerd

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

                  3
                  Online

                  1.1k
                  Users

                  7.0k
                  Topics

                  64.7k
                  Posts