FIXED: VC++ Error R6025 - Can't save & Losing CHOP Export

Not sure quite what happened, but I’ve been able to recreate the bug by opening my project, then opening the Palette dialog, randomly selecting different objects inside the TUIK drop down (like various knobs, sliders, windowparts, etc), then going and selecting UIG. Sometimes it takes about a minute of doing the above before it happens, but I’m able to reliably make it happen.

The error I got was a VC++ R6025.

support.microsoft.com/kb/125749

I got the first error when working on a big project for Saturday. I’ve been able to recreate it in the 18180 build with just the default template. I was using the latest experimental build 18260 when it happened. Since then I tried repairing the installation, and uninstalling it and going back to 18180, and still no luck.

The worst part is that I’m now unable to save certain things, like when I export a chop to a parameter, hit save, and reopen the .toe, it’s as if I had never exported the chop to begin with. The same applies to textarea TUIK components. I can drag one into any project (even the default project), enter it, change the text, save, reopen, and it’s as if the text had never been changed.

Going along with that, the big project I was working on, lost a bunch of random information (like text in the UI, various exported chops, etc), and I would have to go through it all and check everything over to see what happened, which would be a pain but I wouldn’t mind doing, except I tried that, and the not being able to save the things that I fix is stopping me. I’ve attached the project file below and left 2 text Dats in the root where the specific text UI objects and chops I was trying to export are no longer able to be saved.

Im in the midst of updating and trying to repair VC++ incase its the cause, so I’m hoping this will resolve itself so I can use TD on Saturday! If not I’ll have to go back to Resolume until I fix this.

Thanks again for any help!
toika.5.toe (95.5 KB)

Totally forgot to include computer specs. Running Windows 7 professional x64 on a 2010 MacBook Pro with GeForce 330M.

This crash usually means there is some memory corruption occurring in TD, nothing to do with your system or the VC++ install. Can you send us a sample case and how to reproduce it? I’ve love to fix this crash.

With regards to changing nodes and not getting saved, are you sure you arn’t changing nodes inside of a clone? Unless you turn on clone-immune (the lightning bolt on the node), clones will re-recreate themselves on startup from their master component.

Thanks for the speedy reply. Did you try out those steps I mentioned? I’ll make a quick video now of me causing the bug, give me a few minutes to upload it.

I’ll also try out the clone immune right now, thanks for the tip.

When you say you are randomly selecting entries in the TUIK menu, are you dragging them into the network editor, or are you just selecting them? Are you dragging UIG into it? A video of you creating the crash will be excellent

No worries, my instructions were a bit frantic from slightly freaking out last night! Video is being uploaded as I type.

It took about a minute of clicking, maybe because I was doing it with an empty project, but when it first happened to me, it was just one click on UIG and it did what it does at the end of the video. I’ll have a link here in about 2 minutes.

Here it is, tried and true I can make it happen everytime:

divshare.com/download/18598983-415

I’m experimenting with clone immune now, I thought it was working before without, but in reality I may of just left the project open for the past couple days while working on it and never actually opened or closed it till it had crashed. When I set the UI elements to Network Clone Immune it seems to save everything. Do you recommend setting all my UI elements to Network Clone Immune?

Thanks again

Just set the parts that you need to change to clone immune.

So for a textarea TUIK should I clone immune the whole container if I make a change inside or go inside and clone immune just the things I change?

Thank you, I was able to reproduce it. I’ll be able to take a look at this next week I assume.

Great, I’ll avoid clicking around aimlessly in the TUIK. Let me know if you need anything else in regards to the issue.

Thanks again, glad I can use Touch tomorrow! In all honestly, I probably would have used my half working Touch project over Resolume anyways.

It seems like the crash is specific to the UIG component so we’ll look into fixing the case, but at least now we know it’s not a scary crash that can affect playback during a performance or anything.
Thanks for the test case

No worries, good to know.

All the saving/chop exporting things I mentioned were solved with the clone immune function you mentioned (just need to learn what needs to be immune and what doesn’t).

Thanks again.

the UIG crash will be fixed in the next build.

Great to know, looking forward to digging into them next patch. Thanks!