More to the point...why not? Who keeps their PC running day and night? I've been "closing Vegas" (and all other software) for years without problems.

That's a very generic error message, and the URL you linked to about the bins is unrelated -- yours happens at shutdown. Do you have any more of the error message? Or is that all you saw?

It's possible we fixed this same bug recently. We found a place where we shutting down the plugin/effects engine before the scripting engine, so there were dangling references to plugins that no longer existed. This warning might be caused by that same problem. If so, there's no need to worry about it. It happens after your project is already closed, so it should be harmless to your work.

I'm rendering at the moment Chris, but I'll check for more details as soon as I can. This has only reared it's head in the last few days.

Curious. Finished the project. Opened new project. Closed. No error message. Opened the last project that was producing this error EVERY time on closing. Nothing...nada. Sheeeeeeeeeeeeesh....doncha just lurve computers????

OK, thanks anyway for checking Arthur. If it's indeed the bug I think it is, then it might only occurs after you interact with plugins.

I can 100% get a Vegas crash on close if a certain script is opened at some point while Vegas is open. It is the Vegasaur Titles and Text script. You don't actually have to use it, just open it. I have read reports of other Vegas close errors induced/caused by the script subsystem.

I just did this can got the Vegas report dialog and let it send a report in.

Confirmed. I will report it to Vegasaur too.

I reported it to Vegasaur when 1.9 came out, 1.9.1 and 1.9.2 did not change anything. They said they were sorry and do not know what they can do about this.

I did get an email out of the blue about this from Vegasaur when some script bug was fixed in a recent Vegas build. They were wondering if that build fixed this report.

Who knows what or who is the source of the issue. I do trust that Vegasaur would do something about this if they could. Not so sure about Sony. This is not to say Vegasaur is not the source. If it is they simply cannot find a problem.

Stuff is working without error. We have an issue that only shows on shutdown when Vegas closing down and cleaning up its various subsystems. I lean towards Vegas as the instability. Vegasaur is a script setup, not actual code for lack of a better word. A script cannot really pass a bad pointer to Vegas and cause problems. It is in a bit of a protected sandbox of sorts.

I wrote a script system once. VBA language, but a script system nonetheless. No way script code could mess with the underlying application. Bugs in the script system however could do this and this script issue smells like that. Speculation of course.

Vegas scripts can not only mess with the host application but with your whole system and all systems connected to it. That's why it's a good idea to install only scripts from trusted sources, just as with any other software found on the internet.

Nevertheless, it's not unlikely that the upcoming fix mentioned above solves quite a few of these crash on shutdown issues.

Interesting, as I didn't know that scripts could potentially cause those problems. It may be coincidence, but after setting up a Win7/8.1 dual boot, I loaded V12 (Win 8.1) and nothing else. Then gradually loaded my plug-ins and scripts. As soon as I put Vegasaur on the toolbar and opened the backup tool, ALL of my icons on the toolbar disappeared. They need constant rescanning of the script folder to bring back. I also started to get the odd freeze of Mercalli afterwards, which had been working beautifully up to then.

Disappeared icons on the toolbar (actually buttons are there, but the images are not visible) is an old unfixed bug in Vegas Pro. This happens only when a large number of third-party scripts/extensions with custom icons added to the toolbar or menu. They disappear completely random, at different times, even when not using any tool. After rescaning script folder (Tools > Scripting > Rescan Script Menu Folder) all the images become visible again. Anyway, extensions can not add/remove buttons to the toolbar and control their placement.

I hope Chris Dolan also pay attention to this issue.

Probably just coincidence then that Vegasaur was 'the straw that broke the camels back'.

After rescaning script folder (Tools > Scripting > Rescan Script Menu Folder) all the images become visible again.


Thanks for that tip. When that has happened to me, I just closed Vegas and opened it again.

In my case the buttons were still there, just not drawn on the display. If I hovered the mouse over the area, the button outline highlight and tooltip would be displayed.

Just a note: *if* this is the bug I think it is -- and that's a big if -- then we fixed this bug recently (the Movie Studio team found it for their fabulous MS 13 release). It's not a Vegasaur bug, but simply that Vegasaur asks for the plugin list and we shutdown the plugin engine before deleting that list. So when it comes time to delete the list when the app exits, then Vegas panics because there are no plugins anymore so it can't figure out how to close them.

"Probably just coincidence then that Vegasaur was 'the straw that broke the camels back"

I wouldn't be too quick to blame Vegasaur for this problem. I've also experienced this in my Timeline Tools Extension when shutting down Vegas Pro v11; although I receive a different error message. I've traced it back to my Extension programmatically accessing certain properties on certain Vegas Plug-Ins, even though they are never actually used in a project. And this is only an issue with certain Plug-ins. The problem only seems to appear at shutdown, and Vegas operates normally up till the point of shutdown. I've submitted several detailed bug reports on this, only to have them fall into the black hole of Sony support, without even an acknowledgment they were received.

Chris may be right. This may indeed be a shutdown sequence issue inside Vegas.