When I try to customize a base component Touchdesigner gets stuck quite often.
I’ve had TD crash quite a lot the last week (I’m using it quite intensely), often when trying to customize a component (The moment the component editor opens, it gets stuck).
Also when I have a seperate pane on another screen and drag-reference a parameter from one screen to another it often crashes. Sometimes crashes seem to happen quite randomly.
The file I’m working on is a UI so it’s quite a lot of bases and containers connected to eachother.
TD doesn’t make a crashreport or autosave file, it just pops open a windows window
“Touchdesigner is not responding”
This is a google drive link to the toe file. I’m using the paid version of the zerror plugin, so that won’t work too well without a license, I hope that’s not a problem.
When TD is frozen, you can also capture a dump file from the Task Manager by right-clicking on the process and selecting Create Memory Dump File. The file will be very large, but usually compresses well. If you cand send us one of those files we can potentially see where it is stuck.
But, as Ivan said, if you can find a reliable way to reproduce it that would be even better.
I will try to get a dump file asap! Thanks
As I wrote to Ivan, there’s no real reliable way to reproduce it. Sometimes it happens a few times in a row, sometimes it goes 30 minutes without happening.
There you go! Thanks a lot for having a look
This morning Touchdesigner has been closing every minute so I even haven’t been able to properly use it.
It happens more often when adding a duplicate pane and when customizing a container or base comp, though it’s not every time.
Thanks for the file. So it looks like touch is actually stuck in the graphics system when you made this file. It quite likely has something to do with the floating windows you have open rather than anything specifically with the customization dialog.
I assume both screens that you mention are hooked up to that 3070 card?
I’m going to refer it over to one of our graphics developers to see if they have more ideas. How easy it will be to fix will definitely come down to whether we can repeat it here, but if it is happening that often for you then hopefully we can trigger it here
They also have a different refresh rate, I don’t know if that could be of an issue?
I’ll try using TD without external screen for some time and see if I keep getting errors.
Interesting to hear about how the displays are connected. We suspect it might be dependent on a specific system configuration because we haven’t been able to reproduce it ourselves. It would be good to know if it still happens when you disconnect the external screen.
I disconnected my screen this morning and it seems like it happens less, though it didn’t stop from happening completely. Not quite sure what else could be the problem.
Also it really does happen quite often when customizing a component.
I there’s any info or files I could send, let me know!
Cheers
Thanks a lot! I did what you said.
On opening my project file in the TD version you sent me, TD crashes quite fast.
The error appears to be happening in the Zerror component.
With the 120000 version, TD crashes without giving any error message though, so this is new.
Attached you find some screenshots and the crash file.
Thanks for taking your time & let me know if there’s some further testing I can do!
I’ll also try to use the TD version you sent me to do some smaller project today and see if I can get another crash.
Cheers
Edit:
I started working on an new file, and it crashed when I tried customizing a base component. I also had a duplicate pane open. (I tried 2 more times and I only get TD to crash when I have this duplicate pane open)
No error was shown in the extra console window though.
Ok thanks. The new crash you are getting in that MIDI In node is a crash just recently introduced (sorry, this was a daily build I gave you to test).
Let me give you a new one to test in a bit
Hey @malcolm
When you have time, could you send me a new version to test?
Maybe some other ideas how I could test? I’m quite desperate and have a liveshow next saturday
Great. Ive just requested access to the original toe file, if thats still the easiest to duplicate the issue.
We see the problem, but would just like to reproduce it definitively, before applying the fix.
-Rob
