Category Archives: Debugging

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 , | 6 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 , , | 25 Comments

Compiler Tricks to Avoid ABI-Induced Crashes

Posted on December 14, 2022 by brucedawson

Last month I wrote about an odd crash that was hitting a few Chrome users. Something was corrupting the XMM7 register and that was causing Chrome to crash. We fixed a couple of bugs in Chrome and we were able … Continue reading →

Posted in Chromium, Debugging, Investigative Reporting, Symbols | Tagged , , , | 2 Comments

Please Restore Our Registers When You’re Done With Them

Posted on November 21, 2022 by brucedawson

“Hey, you. Yes you, that function over there. When you’re cleaning up please remember to restore all of my registers. Yes, that one too – what do you think this is, Linux?” That’s the problem I was dealing with in … Continue reading →

Posted in Chromium, Debugging, Investigative Reporting, Symbols | Tagged , , | 25 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

The Easy Ones – Three Bugs Hiding in the Open

Posted on August 30, 2020 by brucedawson

I write a lot about investigations into tricky bugs – CPU defects, kernel bugs, transient 4-GB memory allocations – but most bugs are not that esoteric. Sometimes tracking down a bug is as simple as paying attention to server dashboards, … Continue reading →

Posted in Bugs, Code analysis, Code Reliability, Debugging, Floating Point, Linux, Performance | Tagged | 17 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

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

Compiler bug? Linker bug? Windows Kernel bug.

Posted on February 25, 2018 by brucedawson

See the end of the post for an October 2018 bug fix update, or read the whole story: Flaky failures are the worst. In this particular investigation, which spanned twenty months, we suspected hardware failure, compiler bugs, linker bugs, and … Continue reading →

Posted in Debugging, Investigative Reporting, Programming | Tagged , , , | 57 Comments

Zombie Processes are Eating your Memory

Posted on February 11, 2018 by brucedawson

Zombies probably won’t consume 32 GB of your memory like they did to me, but zombie processes do exist, and I can help you find them and make sure that developers fix them. Tool source link is at the bottom. … Continue reading →

Posted in Debugging, Investigative Reporting, Performance, Programming, Rants | Tagged , , | 74 Comments