令人难以置信的逻辑线程数； windbg看不到他们吗？ [英] Incredible number of logical threads; windbg can't see them?

问题描述

我有一个过程，显示约4,294,965,900个当前逻辑线程（根据性能计数器）和约400个物理线程。

I've got a process that is showing ~4,294,965,900 "current logical threads" (according to the performance counters) and ~400 physical threads.

使用ADPlus（-hang）创建了一个内存转储，而windbg（！threads）仅向我显示了物理线程。

I've created a memory dump using ADPlus (-hang), and windbg (!threads) only shows me the physical threads.

如何找出所有这些逻辑线程的位置

How do I find out where all these logical threads are coming from?

推荐答案

我如何找出所有这些逻辑线程的来源？ / p>

How do I find out where all these logical threads are coming from?

不是。它们不存在。您根本无法拥有40亿个任何类型的线程，除非您在64位计算机上运行，​​哦，至少要说几个PB RAM 。

they aren't. They don't exist. You simply can't have 4 billion threads of any kind, unless you're running on a 64-bit machine with, oh, say a couple of petabyte of RAM at the very least.

每个线程，无论是物理操作系统线程还是由某些框架提供，至少都需要某种标识符。如果这是32位数字，则仅存储这些标识符将占用将近16GB的RAM。 （当然，还有大约1600个未使用的标识符）。如果标识符为64位宽，则需要32GB RAM。最重要的是，每个线程都需要一些堆栈空间（通常的默认值为1MB，这使我们最多可以有4 PB的内存）。

Every thread, whether it is a "physical" OS thread or is provided by some framework, need at the very least, some kind of identifier. If that's a 32-bit number then just storing these identifiers will take up nearly 16GB of RAM. (And, of course, you'll have around 1600 unused identifiers left). If the identifiers are 64 bits wide, you need 32GB RAM. On top of that, every thread needs some stack space (a common default is 1MB, which brings us up to 4 petabytes of memory).

这是一个错误。线程不存在，并且性能计数器出于某种原因向您报告垃圾值。

It is a bug. The threads don't exist, and the performance counters are reporting a garbage value to you for some reason or other.

例如，它可能是负错误代码， ，当转换为无符号整数时，将变成这个巨大的数字。

For example, it could be a negative error code which, when converted an unsigned integer, becomes this huge number.

或者可能是其他错误情况。

Or it could be some other error condition.

这篇关于令人难以置信的逻辑线程数； windbg看不到他们吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！