Issue metadata
Sign in to add a comment
|
Fix and re-enable page_cycler.basic_oopif on Android One Perf (1) |
||||||||||||||||||||
Issue descriptionRevision range first seen: Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%281%29?numbuilds=200 +nasko test owner Snippet of log: --------- beginning of crash F/libc (14823): Fatal signal 6 (SIGABRT), code -6 in tid 14823 (chromium.chrome) D/AuthorizationBluetoothService(16780): Received GmsCore event: Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.auth.be.proximity.authorization.bt.AuthorizationBluetoothService$AutoStarter }. E/AuthorizationBluetoothService(16780): Proximity feature is not enabled. V/GmsCoreStatsServiceLauncher(16983): Received broadcast intent Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.common.stats.GmsCoreStatsServiceLauncher } I/DEBUG ( 144): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG ( 144): Build fingerprint: 'google/4560MMX_b/4560MMX_b_sprout:5.1.1/LMY47W/1837160:userdebug/dev-keys' I/DEBUG ( 144): Revision: '0' I/DEBUG ( 144): ABI: 'arm' I/DEBUG ( 144): pid: 14823, tid: 14823, name: chromium.chrome >>> org.chromium.chrome <<< I/DEBUG ( 144): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- I/DEBUG ( 144): Abort message: '[FATAL:compositor_impl_android.cc(462)] Timed out waiting for GPU channel. I/DEBUG ( 144): ' I/DEBUG ( 144): r0 00000000 r1 000039e7 r2 00000006 r3 00000000 I/DEBUG ( 144): r4 b6feae38 r5 00000006 r6 0000000b r7 0000010c I/DEBUG ( 144): r8 b6ebcdd4 r9 beb75fa4 sl 00000000 fp 9afb4e60 I/DEBUG ( 144): ip 000039e7 sp beb75af8 lr b6e77db5 pc b6e9e980 cpsr 600f0010 I/DEBUG ( 144): I/DEBUG ( 144): backtrace: I/DEBUG ( 144): #00 pc 0003d980 /system/lib/libc.so (tgkill+12) I/DEBUG ( 144): #01 pc 00016db1 /system/lib/libc.so (pthread_kill+52) I/DEBUG ( 144): #02 pc 000179c7 /system/lib/libc.so (raise+10) I/DEBUG ( 144): #03 pc 00014169 /system/lib/libc.so (__libc_android_abort+36) I/DEBUG ( 144): #04 pc 000124f0 /system/lib/libc.so (abort+4) I/DEBUG ( 144): #05 pc 01b76f49 /data/app/org.chromium.chrome-1/lib/arm/libchrome_public.so I/ActivityManager( 551): Delay finish: com.google.android.gms/.init.InitializeGmsReceiver
,
Apr 28 2016
===== BISECT JOB RESULTS ===== Status: completed ===== TESTED REVISIONS ===== Revision Exit Code Std Dev N Good? chromium@387596 1 N/A 5 good chromium@387715 1 N/A 5 bad Bisect job ran on: android_one_perf_bisect Bug ID: 607657 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.basic_oopif Test Metric: warm_times/page_load_time Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1289 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014107979463144224 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5803854847803392 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Tests>AutoBisect. Thank you!
,
May 2 2016
Looking at the output a bit closer, it actually looks like the bot IS reproducing the crash since the later revisions are producing a stack trace, while the earlier ones are either passing or failing with a different issue: "AssertionError: Expected total_time > 0, was: 4252017645" I can disable this in the meantime.
,
May 2 2016
,
May 2 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ae15d6d7ba5159ce0c258bfa0da7088e67488ad4 commit ae15d6d7ba5159ce0c258bfa0da7088e67488ad4 Author: simonhatch <simonhatch@chromium.org> Date: Mon May 02 22:16:50 2016 Disable page_cycler.basic_oopif on Android One. TBR=dtu BUG= 607657 CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq Review-Url: https://codereview.chromium.org/1937163002 Cr-Commit-Position: refs/heads/master@{#391067} [modify] https://crrev.com/ae15d6d7ba5159ce0c258bfa0da7088e67488ad4/tools/perf/benchmarks/page_cycler.py
,
May 3 2016
,
Jul 18 2016
,
Dec 21 2016
,
Jan 25 2017
,
Aug 4 2017
This issue was created > 6 months ago. The perf waterfall has changed significantly since then. If this bug is still relevant, please re-open. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by simonhatch@chromium.org
, Apr 28 2016