Forum
    • Categories
    • Register
    • Login

    Nodes compiled, project crashes

    Scheduled Pinned Locked Moved Bug Reports
    5 Posts 2 Posters 31 Views
    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.
    • ustkU
      ustk
      last edited by

      @Christoph-Hart Yep here is the crash stack

      Note that I can now compile the nodes from the wizard as well. In fact I had to open xcode at least once to make the .xcodeproj to be created and found by the wizard...

      So I did compiled the nodes (not the networks) as debug and here's the result:

      Screenshot 2026-01-20 at 12.18.24.png

      Hise made me an F5 dude, any other app just suffers...

      Christoph HartC 1 Reply Last reply Reply Quote 0
      • ustkU ustk referenced this topic
      • Christoph HartC
        Christoph Hart @ustk
        last edited by

        @ustk ah damn, that's a nasty one. I had to refactor some code because if you use parameter value names for parameters, then it allocated the memory on the DLL and deallocated it in the host (HISE), which is a big nononono, but this crash happens in the new code I added to fix that. welp, guess I'm back to the drawing board with this one then.

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

          That's the culprit commit:

          https://github.com/christophhart/HISE/commit/6de7c97b51309f3d6003aefada2480d569eb4a4b

          Can you send me the node that causes this?

          ustkU 1 Reply Last reply Reply Quote 0
          • ustkU
            ustk @Christoph Hart
            last edited by

            @Christoph-Hart Ok cool at least you've got a lead!
            I have many nodes so we never know which one is causing the issue... or can we?

            Hise made me an F5 dude, any other app just suffers...

            Christoph HartC 1 Reply Last reply Reply Quote 0
            • Christoph HartC
              Christoph Hart @ustk
              last edited by

              @ustk you can look up in the stack trace, somewhere you can see the ID of the node that is currently being created, but that's some advanced debugging skill required there :)

              Anyways, I made a few cosmetic changes to the current system which might fix a few trivial issues. Just pull the latest change, if that doesn't help, then I'll rewrite the entire thing (again).

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

              25

              Online

              2.1k

              Users

              13.2k

              Topics

              115.0k

              Posts