Out of memory error

[Paul Gordash]

After leaving the GBPVR.exe program open for about a week, I get the following error message and the screen behind the error message is white with a red x through it.

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

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

************** Exception Text **************
System.OutOfMemoryException: Out of memory.
at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
at System.Drawing.Graphics.DrawImage(Image image, Rectangle destRect, Int32 srcX, Int32 srcY, Int32 srcWidth, Int32 srcHeight, GraphicsUnit srcUnit, ImageAttributes imageAttrs, DrawImageAbort callback, IntPtr callbackData)
at System.Drawing.Graphics.DrawImage(Image image, Rectangle destRect, Int32 srcX, Int32 srcY, Int32 srcWidth, Int32 srcHeight, GraphicsUnit srcUnit, ImageAttributes imageAttr, DrawImageAbort callback)
at System.Drawing.Graphics.DrawImage(Image image, Rectangle destRect, Int32 srcX, Int32 srcY, Int32 srcWidth, Int32 srcHeight, GraphicsUnit srcUnit, ImageAttributes imageAttr)
at ck.a(Boolean& A_0)
at q.r()
at ck.b(String A_0)
at q.a(Message& A_0)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
GBPVR
Assembly Version: 1.0.1984.11204
Win32 Version: 1.0.1984.11204
CodeBase: file:///C:/Program%20Files/devnz/GBPVR/GBPVR.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/winnt/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
GBPVRPublic
Assembly Version: 1.0.1984.11180
Win32 Version: 1.0.1984.11180
CodeBase: file:///C:/Program%20Files/devnz/GBPVR/GBPVRPublic.DLL
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/winnt/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
GBPVRBackendCommon
Assembly Version: 1.0.1984.11199
Win32 Version: 1.0.1984.11199
CodeBase: file:///C:/Program%20Files/devnz/GBPVR/GBPVRBackendCommon.DLL
----------------------------------------
System.Data
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/winnt/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/winnt/assembly/gac/system.serviceprocess/1.0.5000.0__b03f5f7f11d50a3a/system.serviceprocess.dll
----------------------------------------
NativeUtilities
Assembly Version: 1.0.1984.11197
Win32 Version:
CodeBase: file:///C:/Program%20Files/devnz/GBPVR/NativeUtilities.DLL
----------------------------------------
DVDRipperPlugin
Assembly Version: 1.0.1984.11201
Win32 Version: 1.0.1984.11199
CodeBase: file:///c:/program%20files/devnz/gbpvr/gbpvrbackendcommon.dll
----------------------------------------
GBPVRPublic
Assembly Version: 1.0.1984.11180
Win32 Version: 1.0.1984.11199
CodeBase: file:///c:/program%20files/devnz/gbpvr/gbpvrbackendcommon.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/winnt/assembly/gac/system.runtime.remoting/1.0.5000.0__b77a5c561934e089/system.runtime.remoting.dll
----------------------------------------
Microsoft.VisualC
Assembly Version: 7.0.5000.0
Win32 Version: 7.10.3052.4
CodeBase: file:///c:/winnt/assembly/gac/microsoft.visualc/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualc.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (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 machine
rather than being handled by this dialog.


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

This has only started happening with the laster couple of release of GBPVR. I am using and Athlon 1800 with 512mb of ram and W2K with all the latest service packs. It mostly sits at the main menu. I am using the default skin as well with no plugins.

Any help would be appreciated.

Thanks,
Paul

[sub]

Have you got any plugins installed?

[Paul Gordash]

No Sub, no plugins. Just the default install.

Thanks,
Paul

[capone]

Do you have all the updates for .Net? It could be some leak there.

Also, try using leaving it open/running, but not on the main menu screen (or change your loggin lvl). I'm wondering if your log files are getting to big. I don't know if it is fixed, but the default logging setting and the text chaning on the main menu screen gave me some huge log files.

[Paul Gordash]

I have all the updates that MS has on the Windows Update page. I am sure they push .NET upgrades there as well.

The majority of time is spent on the main menu. I can try to leave it on the recordings menu instead and see if that clears anything up.

I am confused on how a logfile (writen to disk) would cause an out of memory error? That would usually cause an out of disk space error.

Sub: Is there anything I can look at as far as log files and such go to see what is happening?

Thanks,
Paul

[sub]

You could try to use Window's perfmon to collect some stats over a week. This should give a more detailed explanation of what is happen with the memory.

I cant say I've noticed it myself. My lounge setup is pretty much left running all the time with the same release as everyone else is running. This machine regularly goes a week or two between restarts. I'll also try to fire perfmon on this to see if I notice anything.

[cheval]

There seems to be a problem here somewhere. I started to get this a few weeks ago and had to reinstall (MVP would no longer stay connected for more than a few seconds). After the reinstall everything worked fine until I applied the latest .NET security update (along with others from windows update) and everything fell apart! Got this memory error, object reference errors, etc.

Reinstal also did not work that time. Something seriously went wrong...

Reinstalled Windows, and GBPVR and everything is back and happy (with the updates).

I'm now doing complete partition backups until I can figure out what happened.

There seems to have been quite a few post recently regarding problems like this.

[sub]

There seems to have been quite a few post recently regarding problems like this.

I've not noticed this. I've been reading everything.

[Paul Gordash]

Sub,

I tried running Perfmon overnight, but did not see a radical jump in the private bytes for the GBPVR process. I'll run it again and take measurements over a week or two.

Thanks,
Paul

[Paul Gordash]

Sub,

I ran Perfmon last night and saw that the private bytes for GBPVR went from 56mb to 3.2gb in 11 hours. I started at 12:00am and saw that the error was up again at 10:00am. Looks like it increased at a steady rate of about 30mb an hour.

I can send you the Perfmon .CSV log file if you'd like to check it out.

Thanks,
Paul