New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 636708 link

Starred by 5 users
Status: WontFix
Owner:
dmazz...@chromium.org
Closed: Oct 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
songsuk@chromium.org
█ durga.behera@chromium.org
mcasas@chromium.org
█ marc...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

Regression: Distortion is seen while rotating display screen from 90deg to 180 degrees

Project Member Reported by sc00335...@techmahindra.com, Aug 11 2016 
Version: 54.0.2824.0/8695.0.0 (Official Build) dev-channel falco,parrot
OS: Chrome os

What steps will reproduce the problem?
(1) Sign in to user >> Check "Highlight the object with keyboard focus when it changes" from Accessibility section of windows
(2) Now rotate screen to 90 degrees using "ctrl+shift+reload" >> Now again change to 180 degress by again using ctrl+shift+reload and observe. 

Expected: No distortion should be seen while rotating screen.
Actual: Instead weird traces is seen while rotating from 90 to 180.

NOTE: On rotating screen crash is seen sometimes[2 out of 5 cases].

Attaching crash ids of same: 0292904100000000, 502a504100000000

This is a regression issue as same is working fine in 53.0.2785.55/8530.49.0 beta channel daisy.

Providing link to video: https://goo.gl/photos/u615ECn3CAs9KxcH6
Actual_distortion.jpg
4.7 MB View Download

Comment 1 by ajha@chromium.org, Aug 11 2016

Cc: songsuk@chromium.org
Components: -UI UI>Accessibility
Labels: ReleaseBlock-Stable
Owner: dmazz...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the crash and the distortion when the screen is rotated on chrome version: 54.0.2824.0/8695.0.0 (Official Build) dev-channel parrot.

Stack trace of crash id: 0292904100000000
==========================================
Thread 0 CRASHED [SIGSEGV @ 0x00000000 ] MAGIC SIGNATURE THREAD
0x00007fd924bbec38	(chrome -screen_rotation_animation.cc:63 )	ash::ScreenRotationAnimation::OnAbort
0x00007fd923fb3c11	(chrome -layer_animation_element.cc:729 )	ui::LayerAnimationElement::Abort
0x00007fd923fb4f50	(chrome -layer_animation_sequence.cc:177 )	ui::LayerAnimationSequence::Abort
0x00007fd923fb86b1	(chrome -layer_animator.cc:937 )	ui::LayerAnimator::ClearAnimationsInternal
0x00007fd923fb87b3	(chrome -layer_animator.cc:66 )	ui::LayerAnimator::~LayerAnimator
0x00007fd923fb8910	(chrome -layer_animator.cc:69 )	ui::LayerAnimator::~LayerAnimator
0x00007fd923fb10c1	(chrome -ref_counted.h:407 )	ui::Layer::SetAnimator
0x00007fd923fb2313	(chrome -layer.cc:105 )	ui::Layer::~Layer
0x00007fd923fb2550	(chrome -layer.cc:120 )	ui::Layer::~Layer
0x00007fd922f14b45	(chrome -accessibility_cursor_ring_layer.cc:39 )	chromeos::AccessibilityCursorRingLayer::~AccessibilityCursorRingLayer
0x00007fd923fadd7c	(chrome -compositor.cc:462 )	ui::Compositor::BeginMainFrame
0x00007fd9240278d1	(chrome -single_thread_proxy.cc:806 )	cc::SingleThreadProxy::DoBeginMainFrame
0x00007fd924027a4e	(chrome -single_thread_proxy.cc:800 )	cc::SingleThreadProxy::BeginMainFrame
0x00007fd921a8885b	(chrome -callback.h:389 )	base::debug::TaskAnnotator::RunTask
0x00007fd921a76405	(chrome -message_loop.cc:496 )	base::MessageLoop::DoWork
0x00007fd921a76d52	(chrome -message_pump_libevent.cc:217 )	base::MessagePumpLibevent::Run
0x00007fd92341d647	(chrome -run_loop.cc:35 )	base::RunLoop::Run
0x00007fd9230f7ec4	(chrome -chrome_browser_main.cc:1967 )	ChromeBrowserMainParts::MainMessageLoopRun
0x00007fd921fbbf1a	(chrome -browser_main_loop.cc:950 )	content::BrowserMainLoop::RunMainMessageLoopParts
0x00007fd921fbd874	(chrome -browser_main_runner.cc:155 )	content::BrowserMainRunnerImpl::Run
0x00007fd921fb8732	(chrome -browser_main.cc:46 )	content::BrowserMain
0x00007fd923099f90	(chrome -content_main_runner.cc:785 )	content::ContentMainRunnerImpl::Run
0x00007fd923098b3a	(chrome -content_main.cc:20 )	content::ContentMain
0x00007fd921d42201	(chrome -chrome_main.cc:85 )	ChromeMain
0x00007fd91f332fb5	(libc-2.19.so -libc-start.c:292 )	__libc_start_main
0x00007fd921d4202b	(chrome + 0x0121202b )	_start

Based on the code search on 'accessibility_cursor_ring_layer.cc' suspecting: https://codereview.chromium.org/2046563009.

dmazzoni@: Could you please take a look at this.

Thank you!

Comment 2 by josa...@chromium.org, Oct 10 2016

Labels: -ReleaseBlock-Stable
Any update here? 
Also, I do not see this in the latest M54 Beta. Is this still reproducible/active?

Comment 3 by mmanchala@chromium.org, Oct 12 2016 

As per comment # 2 verified  Issue on latest M-55.
Issue is not reproducible on 55.0.2883.5/ 8872.3.0 dev Build

Comment 4 by dmazz...@chromium.org, Oct 12 2016

Status: WontFix (was: Assigned)
Marking as WontFix, please reopen if you can repro
►

Sign in to add a comment