This doesn't appear to be an infra bug (i.e. not related to machines failing or misconfigured builders)

-1073741819 = 0xC0000005 and this is a code for Access Violation exception.

Anton, could you supply more information, please: when this flakiness started, how often it happens, stack-trace will be super-helpful.

Last update to brotli was on 2017-06-07
protocol.json.bro was introduced on 2017-05-11

Tested brotli compressing protocol.json with asan/msan/ubsan under linux. All OK.
Is there a way to pick up brotli.exe from a build bot?

Hm, all I know the Windows build failed and closed the tree around 5:44 PST yesterday and the next build passed. I haven't seen this failure again yet.

CCing the third_party/brotli/OWNERS who might know where the binary can be obtained.

This just happened again:

[5182/42951] ACTION //content/browser/devtools:compressed_protocol_json(//build/toolchain/win:x86)
FAILED: gen/blink/core/inspector/protocol.json.bro 
C:/b/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../build/gn_run_binary.py brotli.exe --force --no-copy-stat gen/blink/core/inspector/protocol.json -o gen/blink/core/inspector/protocol.json.bro
brotli.exe failed with exit code -1073741819

https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Win/build
s/22098

Still have no information to diagnose the problem.
Stack trace or binary + minidump would be nice.
Brotli algorithm is "stable", i.e. it does the same thing given the same input.
So, "uncertain" things in execution could only happen in "environment".

FYI this continues to hit the "Google Chrome Win" builder:

https://ci.chromium.org/buildbot/chromium.chrome/Google%20Chrome%20Win/24644
https://ci.chromium.org/buildbot/chromium.chrome/Google%20Chrome%20Win/24694

It looks like this error happens on Dec 9, 10 and 11 (today).

https://ci.chromium.org/buildbot/chromium.chrome/Google%20Chrome%20Win/24731

Again, without support of sheriffs / chromium developers with access to bots, there is nothing I can help with.
Brotli hasn't been updated for a while in Chromium -> sudden spike of "instability" is considered to be caused by environment.

This appears to be a linker bug. Sorry.