Category Archives: Programming

32 MiB Working Sets on a 64 GiB machine

Posted on October 1, 2023 by brucedawson

Memory is a relatively scarce resource on many consumer computers, so a feature to limit how much memory a process uses seems like a good idea, and Microsoft did indeed implement such a feature. However: They didn’t document this (!) … Continue reading →

Posted in Computers and Internet, Investigative Reporting, memory, Performance, Programming, uiforetw, xperf | Tagged , , | 10 Comments

When Debug Symbols Get Large

Posted on March 8, 2023 by brucedawson

TL;DR – upgrade your tools, including Visual Studio, windbg, and Windows Performance Toolkit, if you want to handle Chromium’s symbol files. Details: Death, taxes, and browser engines relentlessly growing – those are the three things that you can really be … Continue reading →

Posted in Debugging, Programming, Symbols, uiforetw, xperf | Tagged , | 12 Comments

No Start Menu for You

Posted on January 17, 2023 by brucedawson

I tend to launch most programs on my Windows 10 laptop by typing the <Win> key, then a few letters of the program name, and then hitting enter. On my powerful laptop (SSD and 32 GB of RAM) this process … Continue reading →

Posted in Code Reliability, Debugging, Investigative Reporting, Performance, Programming, Rants, uiforetw, xperf | Tagged , , | 28 Comments

Determinism Bugs, Part Two, Kernel32.dll

Posted on January 6, 2022 by brucedawson

It was literally the day after I cracked the __FILE__ determinism bug that I hit a completely different build determinism issue. I was asked to investigate why the Chrome build number reported for Chrome crashes on Windows 11 was lagging … Continue reading →

Posted in Bugs, Chromium, Computers and Internet, Investigative Reporting, Programming, Symbols | Tagged , , | 19 Comments

Two Deterministic Build Bugs

Posted on January 4, 2022 by brucedawson

‘Twas the week before Christmas and I ran across a deterministic-build bug. And then another one. One was in Chromium, and the other was in Microsoft Windows. It seemed like a weird coincidence so I thought I’d write about both … Continue reading →

Posted in Bugs, Chromium, Computers and Internet, Debugging, Programming | Tagged , , | 14 Comments

Arranging Invisible Icons in Quadratic Time

Posted on February 16, 2021 by brucedawson

Near the end of January I was pointed to a twitter thread where a Windows user with a powerful machine was hitting random hangs in explorer. Lots of unscientific theories were being proposed. I don’t generally do random analysis of … Continue reading →

Posted in Investigative Reporting, Performance, Programming, Quadratic, Rants, Symbols | Tagged , | 18 Comments

GDI leaks and the importance of luck

Posted on May 10, 2020 by brucedawson

In May 2019 I was asked to look at a potentially serious Chrome bug. I initially misdiagnosed it as unimportant, thus wasting two valuable weeks, and when I rejoined the investigation it was the number one browser-process crash in Chrome’s … Continue reading →

Posted in Bugs, Chromium, Debugging, Programming | Tagged | 25 Comments

Big Project Build Times–Chromium

Posted on March 30, 2020 by brucedawson

A twitter discussion on build times and source-file sizes got me interested in doing some analysis of Chromium build times. I had some ideas about what I would find (lots of small source files causing much of the build time) … Continue reading →

Posted in Chromium, Performance, Programming | Tagged , | 23 Comments

Creating a Public Symbol Server, Easily

Posted on March 14, 2020 by brucedawson

I’ve been a big fan of symbol servers for years. They are a part of the Microsoft/Windows ecosystem that is far better than anything I have seen for other operating systems. With Microsoft’s and Chrome’s symbol servers configured I can … Continue reading →

Posted in Debugging, Programming, Symbols, uiforetw | Tagged | 15 Comments

O(n^2), again, now in WMI

Posted on December 8, 2019 by brucedawson

I recently hit some multi-minute delays on my workstation. After investigating I found that the problem was due to a lock being held for five minutes, and during that time the lock-holder was mostly just spinning in a nine-instruction loop. … Continue reading →

Posted in Investigative Reporting, Programming, Quadratic, Rants, uiforetw, xperf | Tagged , , , , | 23 Comments