TechNewsHeaven {{source.name}}




24-core CPU and I can’t type an email (part one)
2018-08-17T03:30:43Z - brucedawson / Hacker News
Since CFG memory is used to describe executable memory I expected to see one block of CFG memory for each block of executable memory in the process. Instead I saw 98 blocks of executable memory and 24,866 blocks of committed CFG memory. What if memory gets allocated in the CFG bitmap when you allocate executable memory, but it doesn’t get freed when you free the executable memory. After allocating and freeing this many blocks of executable memory this program should sit in a loop where it occasionally try to allocate/free more executable memory, and note when this is slow. Microsoft already fixed their CFG memory scanning performance problems.

Your favorite news


Popular news




Recommended news