WebRTC: Windows 7 debug bots are failing with exit code -1073741819 |
||||
Issue descriptionSince about Thu Oct 27 02:37:59 2016 (time reported by the bot) most executions of rtc_stats_unittests are failing with exit code -1073741819. Example failures: - https://uberchromegw.corp.google.com/i/tryserver.webrtc/builders/win_x64_dbg/builds/2517/steps/rtc_stats_unittests%20on%20Windows-7-SP1/logs/stdio - https://build.chromium.org/p/tryserver.webrtc/builders/win_x64_dbg/builds/2533/steps/rtc_stats_unittests%20on%20Windows-7-SP1/logs/stdio Trybot and bot in the client.webrtc waterfall: - https://build.chromium.org/p/tryserver.webrtc/builders/win_x64_dbg?numbuilds=50 - https://uberchromegw.corp.google.com/i/client.webrtc/builders/Win64%20Debug These failures do NOT seem to be caused by https://codereview.webrtc.org/2442743002 I reverted the CL on this CL and the trybot both fails and succeeds with the CL reverted: https://codereview.webrtc.org/2452373002/#ps40001
,
Oct 27 2016
maruel is this something you've seen or have any advice on how to debug?
,
Oct 27 2016
-1073741819 == 0xC0000005 == access violation, e.g. a crash. Please link to specific swarming tasks if you want me to investigate.
,
Oct 27 2016
Please take a look at - https://chromium-swarm.appspot.com/user/task/321e544883e27110 (first failing task in the main waterfall) - https://chromium-swarm.appspot.com/user/task/321e5e5a95a31010 (first failure in tryserver)
,
Oct 31 2016
Friendly ping.
,
Oct 31 2016
I looked at the inputs (e.g. https://isolateserver.appspot.com/browse?namespace=default-gzip&hash=c09f808f6f6acafefd6fb534faaa6f10d01935b9) but ucrtbased.dll, vccorlib140d.dll and vcruntime140d.dll are there, which would be the most obvious problem there. Try reproducing this on a Windows 7 machine without Visual Studio 2015 installed using "python swarming.py reproduce -S https://chromium-swarm.appspot.com 321e544883e27110" If you don't have one take one Swarming bot down as per internal instructions (how to remote access a bot) and reboot it when done.
,
Oct 31 2016
I ran the command on a Windows 10 machine without Visual Studio. I get the same error code.
,
Oct 31 2016
Should I run it on a Windows 7 machine nonetheless?
,
Oct 31 2016
"I get the same error code." -> debug there if you reproduce.
,
Oct 31 2016
The thing is, if I build and run the same revision locally, it works. And since we made the test run in the bot and not in swarming, it has no problems. Why should the binary be different when built for swarming? I even copied the built file into the 'work' folder that swarming.py downloads, and it works, but I'm not sure how much sense does it make.
,
Oct 31 2016
Maybe it's not mapping all the necessary runtime dependencies? I still don't have any signal that it is an infrastructure problem. I suspect a BUILD.gn configuration error or something like that.
,
Oct 31 2016
Ok, I'll take a look at it. Somewhat unrelated: Do you know if building a binary and copying it inside the 'work' folder that swarming.py downloads is a good way to test a binary in the environment it'd run on swarming?
,
Oct 31 2016
Yes
,
Nov 17 2016
It looks like it fixed itself. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ehmaldonado@chromium.org
, Oct 27 2016