Win32Exception没有足够的存储是可用来处理此命令 [英] Win32Exception Not enough storage is available to process this command
问题描述
通过我的自动碰撞集合 MaxTo 我得到了以下的崩溃报告：
Through my automated crash collection for MaxTo I got the following crash report:
V8.12.0.0 - System.ComponentModel.Win32Exception - :Void UpdateLayered():0
Version: MaxTo8.12.0.0
Exception: System.ComponentModel.Win32Exception
Error message: Not enough storage is available to process this command
Stack trace:
at System.Windows.Forms.Form.UpdateLayered()
at System.Windows.Forms.Form.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(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.Form.WmCreate(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at MaxTo.MainForm.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)
另一个堆栈跟踪：
Another stacktrace:
Version: MaxTo2009.9.0.0
Exception: System.ComponentModel.Win32Exception
Error message: Not enough storage is available to process this command
Stack trace:
at System.Windows.Forms.Form.UpdateLayered()
at System.Windows.Forms.Form.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(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.Form.WmCreate(Message& m)
at System.Windows.Forms.Form.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)
在这个最新的堆栈跟踪也没有提及MaxTo在所有，90％，我得到的崩溃都与堆栈跟踪类似于上面。
In this latest stack trace there is no reference to MaxTo at all, and 90% of the crashes I get are with stack traces similar to the above.
在网上我发现这个错误是平常，如果你忘记释放或处置变量阅读各地。如果通过我的的WndProc ，这似乎有时会出现问题经过寻找，我无法找到挂上引用任何对象一个地方。但所有的变量之一是本地的WndProc，并应因此被垃圾收集方法终止时。
Reading around on the net I find that this error is usual if you forget to release or dispose variables. When looking through my WndProc, which seems to sometimes have the problem pass through, I cannot find a single place that hangs on to references to any objects. All but one of the variables are local to WndProc, and should therefore be garbage collected when the method terminates.
protected override void WndProc(ref Message m)
{
base.WndProc(ref m); // I'm assuming the first trace can be caught here
IntPtr hwnd = m.WParam;
// Our hook tells us something got maximized
if (Win32Import.UWM_MAXIMIZE == (UInt32)m.Msg)
{
// Figure out if we are temporarily disabled or using alternative profiles
KeyStateInfo keyState = KeyboardInfo.GetKeyState(Settings.AlternativeProfileKey);
Rectangle r = FindRectangle(MousePosition, (Settings.EnableAlternativeProfile && keyState.IsPressed ? AlternativeRegions : Regions));
// Did we find a rectangle to place it in?
if (r != Rectangle.Empty)
{
Rectangle position = Win32Import.GetWindowRectangle(hwnd);
Rectangle previousPos = GetLocation(hwnd);
if (position == r && previousPos != Rectangle.Empty)
{
// We are restoring the original position
Win32Import.SetWindowPos(hwnd, IntPtr.Zero, previousPos.X, previousPos.Y, previousPos.Width, previousPos.Height, Win32Import.SWP_NOZORDER | Win32Import.SWP_NOSENDCHANGING);
}
else
{
// We are maximizing to a region
Win32Import.ShowWindow(hwnd, Win32Import.WindowShowStyle.Restore);
Win32Import.SetWindowPos(hwnd, IntPtr.Zero, r.X, r.Y, r.Width, r.Height, Win32Import.SWP_NOZORDER | Win32Import.SWP_NOSENDCHANGING);
// Make sure we remember this location
RememberLocation(hwnd, position);
}
}
}
else if (MaxTo64WindowHandleMessage == m.Msg)
{
// Store the window handle of our 64-bit subprocess
SubProcess64WindowHandle = m.WParam;
}
}
我一直无法重现错误，即使同时运行的程序多天。
I have not been able to reproduce the error, even while running the program over multiple days.
我的假设是，该系统是低或者未分段存储器或GDI处理，但我无法证实这一点的任何地方。似乎没有要对这个错误有什么好的文档。
My assumption is that the system is low on either unfragmented memory or GDI handles, but I cannot confirm this anywhere. There does not seem to be any good documentation on this error.
任何想法，还有什么可能是什么？我可以做任何事情，以prevent这个错误？
Any ideas what else it could be? Can I do anything to prevent this error?
更新：此问题已重新开放，由于缺乏一个像样的解决方案，更多的堆栈跟踪。简单地忽略它并没有解决问题。
Update: The question was reopened with more stack traces, because of the lack of a decent solution. Simply ignoring it does not solve the problem.
推荐答案
泄漏或使用许多GDI对象/句柄。这些可能会导致资源堆不足。您可能无法复制，因为用户可能有其他的GDI资源重程序运行或使用他们这种情况下，终端服务器与其他用户共享一些堆。请参阅<一href="http://stackoverflow.com/questions/507853/system-error-$c$c-8-not-enough-storage-is-available-to-process-this-command">http://stackoverflow.com/questions/507853/system-error-$c$c-8-not-enough-storage-is-available-to-process-this-command
Leaking or using to many GDI objects/handles. Those could cause a resource heap shortage. You might not be able to reproduce because your users might have other GDI resource heavy programs running or use Terminal Server in which case they have to share some of the heap with the other users. See http://stackoverflow.com/questions/507853/system-error-code-8-not-enough-storage-is-available-to-process-this-command
这里你可以阅读有关桌面堆监视器工具来诊断桌面堆问题。
Here you can read about the Desktop Heap Monitor tool to diagnose desktop heap problems.
Here and here and here are GDI leak detection tools.
这篇关于Win32Exception没有足够的存储是可用来处理此命令的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
