Discussion:
Issue 587354 in chromium: Shell Failure: syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
(too old to reply)
c***@googlecode.com
2016-02-17 07:23:25 UTC
Permalink
Status: Untriaged
Owner: ----
CC: ***@chromium.org, ***@chromium.org, ***@chromium.org,
***@chromium.org, ***@chromium.org,
***@chromium.org, ***@chromium.org, ***@chromium.org
Labels: Type-Bug-Regression Pri-1 M-50 OS-Windows Infra-Troopers
Build-Failure

New issue 587354 by ***@chromium.org: Shell Failure: syzygy_optimize
failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

syzygy_optimize failed shell error for Win 32 Build # 50.0.2653.0

Link to the Builder:
---------------------
https://chromegw.corp.google.com/i/official.desktop/builders/win/builds/443

Link to the Error Log:
---------------------
https://chromegw.corp.google.com/i/official.desktop/builders/win/builds/443/steps/shell/logs/stdio

Error Log:
--------------
ERROR:profile:Profiling failed.
Traceback (most recent call last):

File "C:\b\build\slave\win\build\src\third_party\syzygy\binaries\Benchmark_Chrome-0.1-py2.6.egg\profile.py",
line 183, in main
opts.startup_urls)

File "C:\b\build\slave\win\build\src\third_party\syzygy\binaries\Benchmark_Chrome-0.1-py2.6.egg\profile.py",
line 103, in ProfileChrome
chrome_runner.Run(iterations)

File "C:\b\build\slave\win\build\src\third_party\syzygy\binaries\Benchmark_Chrome-0.1-py2.6.egg\runner.py",
line 355, in Run
self._RunOneIteration(i)

File "C:\b\build\slave\win\build\src\third_party\syzygy\binaries\Benchmark_Chrome-0.1-py2.6.egg\runner.py",
line 415, in _RunOneIteration
chrome_control.ShutDown(self._profile_dir)

File "C:\b\build\slave\win\build\src\third_party\syzygy\binaries\Benchmark_Chrome-0.1-py2.6.egg\chrome_control.py",
line 101, in ShutDown
raise ChromeNotFoundException
ChromeNotFoundException
Traceback (most recent call last):

File "..\..\..\..\build_internal\scripts\slave-internal\syzygy_optimize.py",
line 266, in <module>
sys.exit(main(_ParseArgs()))

File "..\..\..\..\build_internal\scripts\slave-internal\syzygy_optimize.py",
line 249, in main
_GetCallTraces(build_dir, product_dir, calltrace_dir)

File "..\..\..\..\build_internal\scripts\slave-internal\syzygy_optimize.py",
line 119, in _GetCallTraces
_ProfileChrome(build_dir, instrumented_dir, trace_dir, 'calltrace')

File "..\..\..\..\build_internal\scripts\slave-internal\syzygy_optimize.py",
line 97, in _ProfileChrome
*mode_args)

File "..\..\..\..\build_internal\scripts\slave-internal\syzygy_optimize.py",
line 67, in _Shell
raise _SubprocessError('Command "%s" returned %d.' % (cmd, retcode))
__main__._SubprocessError:
Command "('src\\out\\..\\third_party\\syzygy\\binaries\\profile.bat', '--verbose', '--input-dir', 'src\\out\\Release\\calltrace\\instrumented', '--output-dir', 'src\\out\\Release\\calltrace\\trace', '--iterations', '20')"
returned 1.
program finished with exit code 1
elapsedTime=598.448000

adding waterfall sheriffs & troopers

could someone please look into this issue?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 07:49:00 UTC
Permalink
Updates:
Status: Assigned
Owner: ***@chromium.org
Cc: ***@chromium.org ***@chromium.org ***@chromium.org
syzygy-***@chromium.org

Comment #1 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

Providing the CL details --
https://chromium.googlesource.com/chromium/src/+log/50.0.2652.0..50.0.2653.0?pretty=fuller&n=10000

Suspecting Commit# 365cf04600cd4126bc3fa6e62820d4d712f959ad
Suspecting Review URL# https://codereview.chromium.org/1700113003

@pmonette -- Could you please look into the issue, pardon me if it has
nothing to do with your changes and if possible please assign it to the
concern Dev.

Note: Also adding syzygy-***@chromium.org as the failure is related.

Thank You.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 08:24:30 UTC
Permalink
Updates:
Cc: ***@chromium.org

Comment #2 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

Another possible suspect : https://codereview.chromium.org/1693433004

Please reassign if this is not related to your change.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 09:26:45 UTC
Permalink
Updates:
Cc: ***@chromium.org

Comment #3 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

(No comment was entered for this change.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 15:09:19 UTC
Permalink
Updates:
Cc: ***@chromium.org

Comment #4 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

I don't think that Patrick is an appropriate owner for this one, it's
related to Syzygy directly.

There's a few error message like this one emitted by crashpad:
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffde000, size 0x230
fully unreadable

Could it be a OOM ?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 15:55:46 UTC
Permalink
Updates:
Owner: ***@chromium.org

Comment #5 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

(No comment was entered for this change.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 16:40:48 UTC
Permalink
Comment #6 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

Looks like Chrome's crashing in a profile iteration. Works fine 13 times,
but the 14th iteration crashes.
Unfortunately it doesn't look like CrashPad uploaded the crash dump from
this, though that would've been awesome. Scott - is there something simple
we can do, like set an environment variable to "consent" for crash uploads
on build machines?

INFO:runner:Starting iteration 14.
INFO:runner:Starting RPC logging.
INFO:runner:Iteration: 14
INFO:runner:Launching command line
[['C:\\b\\build\\slave\\win\\build\\src\\out\\Release\\calltrace\\instrumented\\chrome.exe', '--user-data-dir=C:\\b\\build\\slave\\win\\build\\src\\out\\Release\\calltrace\\trace\\profile', '--noerrdialogs']].
INFO:runner:Looking for Chrome instance with profile_dir
C:\b\build\slave\win\build\src\out\Release\calltrace\trace\profile.
INFO:runner:Looking for Chrome instance with profile_dir
C:\b\build\slave\win\build\src\out\Release\calltrace\trace\profile.
[6064:5092:0216/224642:ERROR:browser_gpu_channel_host_factory.cc(120)]
Failed to launch GPU process.
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffde000, size 0x230
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffdd000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffda000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffd7000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffaf000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffac000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffa9000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffa3000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffa0000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfffa6000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff9d000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff9a000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff97000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff94000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff91000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff8e000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff8b000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff88000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff85000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff82000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff7f000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff7c000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff79000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff76000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff73000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff70000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff6d000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff6a000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff67000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff64000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff61000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff5e000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff5b000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff58000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff55000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff52000, size 0xf84
fully unreadable
[0216/224653:ERROR:process_info.cc(608)] range at 0xfff4f000, size 0xf84
fully unreadable
INFO:runner:Shutting down Chrome Profile:
C:\b\build\slave\win\build\src\out\Release\calltrace\trace\profile
ERROR:runner:Failure in iteration 14.
Traceback (most recent call last):

File "C:\b\build\slave\win\build\src\third_party\syzygy\binaries\Benchmark_Chrome-0.1-py2.6.egg\runner.py",
line 355, in Run
self._RunOneIteration(i)

File "C:\b\build\slave\win\build\src\third_party\syzygy\binaries\Benchmark_Chrome-0.1-py2.6.egg\runner.py",
line 415, in _RunOneIteration
chrome_control.ShutDown(self._profile_dir)

File "C:\b\build\slave\win\build\src\third_party\syzygy\binaries\Benchmark_Chrome-0.1-py2.6.egg\chrome_control.py",
line 101, in ShutDown
raise ChromeNotFoundException
ChromeNotFoundException
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 17:18:55 UTC
Permalink
Comment #7 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

Why is crashpad trying to grab some memory ranges in the kernel address
space ?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 17:43:55 UTC
Permalink
Comment #8 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

This looks like the Chrome process itself crashed, and then crashpad
started taking a crash dump. The failure messages from crashpad are it
complaining about memory not being readable across process boundaries, so
likely nothing to do with OOM.

The Syzygy error message is simply it complaining that the Chrome process
failed to start.

So, likely symptomatic of a bigger problem that has nothing to do with
Syzygy. Did crashpad upload a crash for this failure that we can find? That
might have more information.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-18 09:33:46 UTC
Permalink
Comment #14 on issue 587354 by ***@chromium.org: Shell Failure:
syzygy_optimize failed shell error for Win 32 Dev Build # 50.0.2653.0
https://code.google.com/p/chromium/issues/detail?id=587354

Just to update, the next Windows 32 build # 50.0.2654.0 has been compiled
successfully without any errors. Please find the Bot details below,

https://chromegw.corp.google.com/i/official.desktop/builders/win/builds/449

Note: Adding Restrict View as the issue contains bot URLs.
Thank You.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
Loading...