为什么我的 Windows 程序会死掉并显示冻结（蓝灰色）的窗体或窗口？
我在 Windows 7 上的 delphi 程序（不适用于 .NET）似乎连续运行了几天，然后该程序有点冻结，其所有窗口都涂上了蓝灰色，就好像其窗口被禁用一样。您根本无法再控制该程序，而必须终止其进程并重新启动它。您不需要重新启动系统本身。
有没有人经历过这个或类似的事情？如果是这样，您采取了什么措施来解决或尝试解决它？
谢谢，
My delphi program (NOT for .NET) on windows 7 seems to be running for couple of days straight and then the program sort of freezes with all of its windows painted with blueish grey color as if its windows are disabled. You simply don't have control over the program anymore but has to kill its process and start it up again. You don't need to reboot the system itself.
Has anyone experience this or anything similar? If so, what did you do to resolve or try to resolve it?
Thanks,
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
你的问题上下文非常模糊。我们没有关于您的应用程序的任何信息，甚至其设计和架构。
尽管如此，我的（通用）建议如下：
Synchronize调用进行的；我的 Delphi 应用程序运行了几个月没有任何问题。问题肯定是在应用程序代码中，而不是在 Delphi 架构中（它的 RTL 和 VCL 非常稳定）。
Your question context is very vague. We do not have any information about your application, even its design and architecture.
Nethertheless, my (general-purpose) suggestions are the following:
Synchronizecall;I've Delphi application running for months without any problem. Issue is definitively in application code, not in the Delphi architecture (its RTL and VCL are very stable).
蓝灰色可能是默认的窗口颜色，这意味着窗口不再自行绘制。这与程序不再响应任何输入的另一个症状一致。这意味着它不处理任何窗口消息。
最简单的调试方法是在调试器中运行程序，当程序挂起时，将其停止并查看它在哪里。
如果发生内存泄漏，您最终可能会耗尽进程空间中的内存，并且程序可能无法正确响应该情况。检查任务管理器以查看其使用的内存量。
The bluish grey color is probably the default window color, meaning the window is no longer painting itself. This is consistent with the other symptom that the program no longer responds to any input. This means it isn't processing any window messages.
The easiest way to debug is to run the program in a debugger, and when it's hung just stop it and see where it's at.
If you have a memory leak you may eventually run out of memory in your process space, and it's possible that the program doesn't properly respond to that condition. Check Task Manager to see the amount of memory it's using.
是的，我在过去几年修复了一些挂起和其他问题。
我之前使用过ProcessExplorer（查看堆栈），但它需要Microsoft调试符号。使用 Delphi，您只能创建 .map 文件。使用map2dbg，我可以将.map转换为.dbg，但这并不总是有效（注意：.dbg已被弃用，较新版本的Microsoft调试工具不再使用它们）。
所以我制作了自己的工具:-)
它是“AsmProfiler Sampling”工具的一部分：
http://code.google.com/p /asmprofiler/downloads/detailname=AsmProfiler_Sampling%20v1.0.7.13.zip
点击第一个屏幕中的“进程堆栈视图”按钮。
然后从列表中选择您的进程并双击它：
http://code.google.com/p/asmprofiler/wiki/ProcessStackViewer
现在您可以查看每个线程的堆栈跟踪。如果 GUI 没有响应，则主线程挂起，因此请检查第一个线程。 （注意：有时您会看到一个“空”堆栈，因为函数未对齐堆栈进行计算等，请使用原始轨迹跟踪算法再次获取更多完整堆栈（有很多误报，因为堆栈上的每个指针都是可能会显示一个函数！））。
如果您无法解决，请将堆栈贴在这里，以便我们查看。
注意：它使用 JEDI 库的 jclDebug.pas 单元，因此它可以读取 .map 和 .jdbg 文件（也可以读取 Windows dll 的 .dbg 和 .pdb 调试文件）以及内部 JCLDEBUG 部分（在一个 . EXE文件）。因此，您至少必须构建一个包含详细（！）映射文件的 .exe，请参阅项目选项 ->编译器->链接。
Yes I fixed several hangs and other problems in the past years.
I used ProcessExplorer before (to view the stack), but it needs Microsoft debug symbols. And with Delphi you can only create a .map file. With map2dbg I could convert the .map to a .dbg, but this does not always work (note: .dbg is deprecated, newer versions of Microsoft debugging tools do not use them anymore).
So I made my own tool :-)
It is part of "AsmProfiler Sampling" tool:
http://code.google.com/p/asmprofiler/downloads/detailname=AsmProfiler_Sampling%20v1.0.7.13.zip
Click on the "Stack view of Process" button in the first screen.
Then select your process from the list and double click on it:
http://code.google.com/p/asmprofiler/wiki/ProcessStackViewer
Now you can view the stack trace of each thread. If the GUI does not respond, the main thread hangs, so check the first thread. (note: sometimes you see an "emtpy" stack because a function misaligned the stack for calculation etc, use the raw strack tracing algoritm to get more the full stack again (with a lot of false positives, because every pointer on the stack which is possible a function is shown!)).
Please post the stack here if you can't solve it, so we can take a look at it.
Note: it uses the jclDebug.pas unit of the JEDI library, so it can read .map and .jdbg files (also .dbg and .pdb debug files of Windows dlls) and also internal JCLDEBUG sections (embedded .jdbg file in one .exe). So you must at least build an .exe with detailed (!) map file, see Project Options -> Compiler -> Linking.