L
Liverpool fan
I have a VB .NET windows application that is throwing an intermittent
'out of memory' error. Here is the call stack.
Out of memory.
at System.Drawing.Graphics.FromHdcInternal(IntPtr hdc)
at System.Windows.Forms.DibGraphicsBufferManager.CreateBuffer(IntPtr
src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
at
System.Windows.Forms.DibGraphicsBufferManager.AllocBuffer(Graphics
targetGraphics, IntPtr targetDC, Rectangle targetBounds)
at System.Windows.Forms.DibGraphicsBufferManager.AllocBuffer(IntPtr
target, Rectangle targetBounds)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
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) Source = System.Drawing
The program uses our own timer form that gives a countdown between each
processing cycle. Each processing cycle looks for reports that need
running from 3 SQL Server 2000 databases (don't ask why there are
three). Also, once a day it does a bcp load of data into each of the 3
database and runs various snapshot tasks.
I don't think the details are important besides to say it is doing a
fair amount of processing.
The question is, is this likely to be caused by memory leakage. Sounds
like it to me but I thought that I'd find out if anybody else gets this
error. The call stack is always the same but it fails at various times
of day but sometimes not for 2 weeks.
I have been monitoring the memory usage and it does go up gradually
over time from 120Mb to 150Mb. I have added garbage collection calls to
no effect.
The program uses COM in various places.
Any advice greatly appreciated.
'out of memory' error. Here is the call stack.
Out of memory.
at System.Drawing.Graphics.FromHdcInternal(IntPtr hdc)
at System.Windows.Forms.DibGraphicsBufferManager.CreateBuffer(IntPtr
src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
at
System.Windows.Forms.DibGraphicsBufferManager.AllocBuffer(Graphics
targetGraphics, IntPtr targetDC, Rectangle targetBounds)
at System.Windows.Forms.DibGraphicsBufferManager.AllocBuffer(IntPtr
target, Rectangle targetBounds)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
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) Source = System.Drawing
The program uses our own timer form that gives a countdown between each
processing cycle. Each processing cycle looks for reports that need
running from 3 SQL Server 2000 databases (don't ask why there are
three). Also, once a day it does a bcp load of data into each of the 3
database and runs various snapshot tasks.
I don't think the details are important besides to say it is doing a
fair amount of processing.
The question is, is this likely to be caused by memory leakage. Sounds
like it to me but I thought that I'd find out if anybody else gets this
error. The call stack is always the same but it fails at various times
of day but sometimes not for 2 weeks.
I have been monitoring the memory usage and it does go up gradually
over time from 120Mb to 150Mb. I have added garbage collection calls to
no effect.
The program uses COM in various places.
Any advice greatly appreciated.