NEW CRASH IN V8 ... COOL!

Darren Powell wrote on 3/5/2008, 3:36 PM
Here's a new one ... just been creating some titles in ProType in V8 to render out and use in my Vegas 7d project ... and this cool message just appeared ...

It's got some cool stuff about 'OutOfMemory' problems (surprise surprise considering I've got 4GB and a quad) and something about some Jitterbugging as well ...

Check it out Sony!

Darren Powell
Sydney Australia

-------------------------------------------------------------

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at Sony.MediaSoftware.TextGen.CoreGraphics.PlayState.Seek(Double position, Boolean moveAnchor)
at Sony.MediaSoftware.TextGen.WidgetLibrary.TimelineEditor.SetCursorPosition(Double time)
at Sony.MediaSoftware.TextGen.WidgetLibrary.TimelineEditor.TimelineEditor_Drag(Point ptDelta, MouseState ms)
at Sony.MediaSoftware.TextGen.CoreUI.Widget.OnDrag(Point ptDelta, MouseState ms)
at Sony.MediaSoftware.TextGen.CoreUI.WidgetHost.form_MouseMove(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseMove(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseMove(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at Sony.MediaSoftware.TextGen.ControlLibrary.WidgetHostControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Interop
Assembly Version: 1.0.0.217
Win32 Version: 1.0.0.217
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/Interop.DLL
----------------------------------------
CoreGraphics
Assembly Version: 1.0.0.217
Win32 Version: 1.0.0.217
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CoreGraphics.DLL
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
CorePrimitives
Assembly Version: 1.0.0.217
Win32 Version: 1.0.0.217
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CorePrimitives.DLL
----------------------------------------
CoreGraphics.XmlSerializers
Assembly Version: 1.0.0.217
Win32 Version: 1.0.0.217
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CoreGraphics.XmlSerializers.DLL
----------------------------------------
PresentationCore
Assembly Version: 3.0.0.0
Win32 Version: 3.0.6920.0 (vista_rtm_wcp.061020-1904)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/PresentationCore/3.0.0.0__31bf3856ad364e35/PresentationCore.dll
----------------------------------------
WindowsBase
Assembly Version: 3.0.0.0
Win32 Version: 3.0.6920.0 (vista_rtm_wcp.061020-1904)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/WindowsBase/3.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
WidgetLibrary
Assembly Version: 1.0.0.217
Win32 Version: 1.0.0.217
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/WidgetLibrary.DLL
----------------------------------------
CoreUI
Assembly Version: 1.0.0.217
Win32 Version: 1.0.0.217
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CoreUI.DLL
----------------------------------------
CoreUI.XmlSerializers
Assembly Version: 1.0.0.217
Win32 Version: 1.0.0.217
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CoreUI.XmlSerializers.DLL
----------------------------------------
System.Data.SqlXml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Data.SqlXml/2.0.0.0__b77a5c561934e089/System.Data.SqlXml.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
ControlLibrary
Assembly Version: 1.0.0.217
Win32 Version: 1.0.0.217
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/ControlLibrary.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Comments

busterkeaton wrote on 3/5/2008, 3:56 PM
Have you send the veg file into Sony technical support?
Serena wrote on 3/5/2008, 7:26 PM
Not much use posting the debug message here unless you're hoping a user knows the fix.
CorTed wrote on 3/5/2008, 7:58 PM
You know Darren, I think Serena is right.... if you expect Sony to really care about your debug message, they would have commented/fixed/or said something months ago.
There are serious memory/crash problems with V8.
But appearently they (SCS) thinks v8b is the answer.
So enjoy v8b everyone.... oh, and don't expect a reply from Sony
Darren Powell wrote on 3/5/2008, 10:28 PM
Yeh, I'm hoping a user will hack the Vegas exe and fix it.

Cheers,

Darren Powell
Sydney Australia
farss wrote on 3/6/2008, 3:25 AM
Probably more chance of that happening than SCS fixing it.

One naughty thought did enter my head, every time it crashes I get a popup asking me if I'd like to send a report to Microsoft. Maybe if we flooded Microsoft with crash dumps they'll do something.
Yeah, I know, day dreaming again.

Bob.
winrockpost wrote on 3/6/2008, 6:33 AM
this is getting beyond ridiculous, you guys have so much more patience than me. I'd have fired up edius or premiere or whatever long ago.
Weird thing I have had a few hangs with vegas and see it chewing up memory but no slam bam crashes , never used the new title thing though.
Come on Sony you got something seriously wrong here.

Udi wrote on 3/6/2008, 11:27 PM
Darren,

Memory exception is related to virtual memory - not real memory.
It can happen if you don't have enough paging space or the program VM can't be expanded for some other reason.

Udi
Steve Mann wrote on 3/7/2008, 2:25 PM
I worked as a software engineer for several years, and if the problem can't be reproduced by someone else, it's highly unlikely to be a bug in the application. Also, if the software developer can't reproduce the problem, how the hell are they supposed to fix it?

I have never had a crash while running Vegas, DVDA or, come to think of it, anything else. But I do not allow Windows to control my Virtual Memory.

Steve
farss wrote on 3/7/2008, 2:36 PM
"Also, if the software developer can't reproduce the problem, how the hell are they supposed to fix it?"

You do what we used to do. You buy the slackers a one way ticket to wherever the problem is. They get the ticket home when they fix their screwup.
I'd point out that Vegas is sold as "hardware agnostic". Well if it crashes because of certain hardware configurations (i.e. using a quad core) that aren't defective then it's simply false advertising.
I'd also point out that years ago software was one hell of a lot easier to write. Multithreading introduces all manner of issues that can be very tricky to replicate in your lab unless you've got a very wide range of hardware and test scenarios. So yeah we're all the alpha testers. That's fine, no problem with that. What's missing in the picture is any sign of interest in out results and any sign of any effort to get out of Maddison and go fix the problem at the coal face.

Bob.
Steve Mann wrote on 3/7/2008, 2:46 PM
Based on my experience as a software engineer and later a tech support manager, the reality is that if they can't reproduce the problem and they have relatively few complaints about it, it becomes a low priority. When we had the time or the priority was increased by people at a higher pay scale than mine, the problem invariably turned out to be a poorly written process or driver code that we did not install. Only once in the years in the tech support job can I recall a customer complaint actually uncovered a bug in our BIOS.

If a hundred users complained about the same problem that couldn't be reproduced in the lab, then we would go to a strategically important customer's location to investigate. That, too, was rare.
CorTed wrote on 3/7/2008, 4:22 PM
These problems that have been reported on this forum (and many others that I view) I feel should be enough to spark some interest by the SCS team. If you would do a search on this forum alone the various crashing scenarios, which appear to be more prevelant on quad core machines seem real enough. I would certainly hope it is not LOW priority.
SCS may be working on a fix, but as Bob said the silence out of the support team on this forum, and remember it is a genuine Sony Forum, is almost scary.
V8 IMHO has been a release which seem to have more crashing problems than any of the previous releases, and hence appears to be the least stable version.
If Vegas V8 wants to be a real player in the PRO NLE sandbox, I think they need to turn up the priority on fixing the problems.

Ted
ForumAdmin wrote on 3/7/2008, 6:14 PM
re the original post in this thread:

Can you provide repo steps? If so please submit them to SCS support and we'll try to fix the issue in a future release, hopefully the next point release.

We need 1,2 3 repro steps. A random crash, as others pointed out, is often very hard to track down. Since this doesn't appear (from your post) to be media related, if you have a 100% crash repro on render, please submit the .veg file when you email our support team, and include your render settings also.

thanks

-SCS dev