Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by madeofpalk | Hacker News Reader

Parent Full thread

madeofpalk·

> Unfortunately, with access to neither the Chrome source code

I mean, you basically do! You can just go check out the chromium source.

View on HN

> I mean, you basically do! You can just go check out the chromium source.

It's mentioned in the bullet points in the "trouble reproducing the bug" section that chromium wasn't affected.

> Using open-source Chromium instead of Chrome did not cause crashes, so we couldn’t see what Chrome code was failing either.

Google provides symbols for Chrome release builds, including source indexing so source code should be available. See sections symbol server and source indexing at https://www.chromium.org/developers/how-tos/debugging-on-win...

I wish this was upvoted more. This is the correct way to troubleshoot the bug, full stop. You can get symbolic stack traces with full arguments and source code on Windows in about 5-10 minutes for any Chrome crash by following these instructions. I always have a last change exception handler that fires up a WinDBG script on Windows for our chromium-based test runners, which reduces troubleshooting time to just a couple minutes in order to find the symbol in their bug database. Playing blackbox what-if games like the Gusto team is a waste of time and doesn't contribute any situation-specific knowledge to bugs.chromium.org.

Only for Windows. For some reason they don’t make their symbols for Mac public…

I wonder what version of Chromium they used. If it was a nightly, it could be weeks before the fix makes it into Chrome. They might've tested at a time when latest Chrome had the bug and Chromium didn't.

Reply on news.ycombinator.com