Project with nPass Graph crashes when loaded

InstaMAT
1

Hi! I’ve recently been playing around with InstaMAT. I have a small project that crashes whenever I try to load it.

I created this while adding an nPass Graph to an Element Graph and then saving. While it’s not a set of repro steps, this is just what I can remember doing, so it might not be fully accurate:

  • I created a new nPass graph, added a few string operations to it, and a nPass stringElement variable
  • I opened one of my other element graphs
  • I dragged the unsaved nPass graph into the element graph
  • The node was outlined in red
  • I saved the project
  • InstaMAT crashed

Now I have a project that crashes every time I try to open it.

There is no crash report that I could find. There is no CrashReports folder in my Documents\InstaMAT folder.

Here’s a zip of my IMP file that crashes. Unnamed Element.zip (8.1 MB)

I’m going to see if I can find out what specifically caused the broken project in the first place, but I’ve had no luck so far.

Does this project crash for anyone else?

2

Figured out how to repro this! It’s easier than I thought:

  • ctrl+N and choose nPass Element Graph OR Element Graph
  • drag the unsaved graph into its own canvas. The node will be outlined in red. Do NOT reposition it after dragging it in
  • save
  • drag the node to reposition it. InstaMAT will crash

Any future attempts to open that project will immediately crash. Here’s an example of such a project:
borked.IMP (2.1 KB)

This can basically brick a project. Is there a way to recover from this?

3

Hello @uber5001, thanks a lot for the report!

I gave both of your packages a try, and on my end, neither of them is crashing. I do see the errors showing up in the graph, though. Just a heads-up: it’s not possible to instance a graph into itself — but even so, it definitely shouldn’t be causing a crash.

I also followed your reproduction steps, and I am not able to reproduce it unfortunately.

Would you mind sharing your system specs and OS? That might help us figure out what’s going on.

When there is nothing in the crash reports folder, I assume it crashes without a crash log?

Thanks!

4

My specs:

  • Windows 11 Pro 64-bit, Version 10.0.26100 Build 26100
  • i9-12900KF
  • RTX 3080 TI
  • 32 GB RAM
    Full specs from msinfo32 and dxdiag:
    specs.zip (316.4 KB)

Yes, it seems to crash without a log. The Documents\InstaMAT\CrashReports folder doesn’t even exist, so I assume there’s no crash log. My project is located in Documents\InstaMAT\Library\borked.IMP.

1 Like
5

I’ve reproduced the issue on a different machine with a fresh install of InstaMAT Studio. Windows 10 Pro. Version 10.0.19045 Build 19045

Specs:
specs.zip (423.8 KB)
IMP:
Unnamed Element.IMP (1.2 KB)

1 Like
6

was able to reproduce the same crash on windows 10 pro 64-bit (10.0, Build 19045)

1 Like
7

Thank you @uber5001, we’ll take a deeper look into the issue.

@Konnivee welcome to the community! Thanks for posting and confirming you can reproduce the crash. We’ll take a look at that.

8

Thanks @uber5001 and @Konnivee for reporting and reproducing the crash. I’ve tested the steps and the package on mac and haven’t been able to reproduce it. We’ll continue to investigate.

Thanks again!

1 Like