Issue metadata
Sign in to add a comment
|
Regression: Browser crashes when there are more number of pinned apps and chromevox enabled |
||||||||||||||||||||||
Issue descriptionVersion: 52.0.2739.0/8349.0.0 (Official Build) dev-channel samus,link,alex OS: chrome os What steps will reproduce the problem? (1) Enable Chromevox from OOBE screen >> Login with valid credentials (2) Pin more number of apps so that overflow button appears[Or sign in with account that has many pinned apps in uber tray] and observe Expected: Browser should not crash when there are more number of pinned apps and chromevox enabled Actual: Instead browser crashes. Crash ids: 8e34e66a00000000, 0c38e66a00000000 This is a regression issue as it is not seen in 47.0.2526.106/7520.63.0 stable channel daisy. Issue is also seen in 50.0.2661.103/7978.74.0 stable channel daisy.
,
May 20 2016
Able to reproduce the issue on Link using chrome version 52.0.2739.0/8349.0.0 Stack trace ============== Thread 0 CRASHED [SIGSEGV @ 0x00000000 ] MAGIC SIGNATURE THREAD 0x00007f56c6aa2d10 (chrome -shelf_view.cc:547 ) ash::ShelfView::GetTitleForView 0x00007f56c6afa55a (chrome -shelf_button.cc:383 ) ash::ShelfButton::GetAccessibleState 0x00007f56c7244812 (chrome -ax_view_obj_wrapper.cc:50 ) views::AXViewObjWrapper::Serialize 0x00007f56c687c358 (chrome -ax_tree_source_aura.cc:117 ) AXTreeSourceAura::SerializeNode 0x00007f56c687ac62 (chrome -ax_tree_serializer.h:496 ) ui::AXTreeSerializer<views::AXAuraObjWrapper*, ui::AXNodeData, ui::AXTreeData>::SerializeChangedNodes 0x00007f56c687b1a2 (chrome -ax_tree_serializer.h:528 ) ui::AXTreeSerializer<views::AXAuraObjWrapper*, ui::AXNodeData, ui::AXTreeData>::SerializeChangedNodes 0x00007f56c687b802 (chrome -ax_tree_serializer.h:382 ) ui::AXTreeSerializer<views::AXAuraObjWrapper*, ui::AXNodeData, ui::AXTreeData>::SerializeChanges 0x00007f56c687ba1a (chrome -automation_manager_aura.cc:145 ) AutomationManagerAura::SendEvent 0x00007f56c687bdf1 (chrome -automation_manager_aura.cc:78 ) AutomationManagerAura::HandleEvent 0x00007f56c72310b3 (chrome -view.cc:1336 ) views::View::NotifyAccessibilityEvent 0x00007f56c7234c51 (chrome -view.cc:418 ) views::View::SetVisible 0x00007f56c6aa21e0 (chrome -shelf_view.cc:901 ) ash::ShelfView::CalculateIdealBounds 0x00007f56c6aa3d45 (chrome -shelf_view.cc:1550 ) ash::ShelfView::ShelfItemAdded 0x00007f56c6a9fa73 (chrome -shelf_model.cc:63 ) ash::ShelfModel::AddAt 0x00007f56c6955b7b (chrome -chrome_launcher_controller.cc:1662 ) ChromeLauncherController::InsertAppLauncherItem 0x00007f56c6957230 (chrome -chrome_launcher_controller.cc:1216 ) ChromeLauncherController::UpdateAppLaunchersFromPref 0x00007f56c79582e2 (chrome -extension_registry.cc:54 ) extensions::ExtensionRegistry::TriggerOnLoaded 0x00007f56c7762b25 (chrome -extension_service.cc:1056 ) ExtensionService::NotifyExtensionLoaded 0x00007f56c77647eb (chrome -extension_service.cc:1521 ) ExtensionService::AddExtension 0x00007f56c775e2ca (chrome -extension_service.cc:1913 ) ExtensionService::FinishInstallation 0x00007f56c775edd4 (chrome -extension_service.cc:1890 ) ExtensionService::FinishDelayedInstallation 0x00007f56c775da8b (chrome -extension_service.cc:1877 ) ExtensionService::MaybeFinishDelayedInstallation 0x00007f56c4839f15 (chrome -bind_internal.h:186 ) base::internal::Invoker<base::IndexSequence<0ul, 1ul>, base::internal::BindState<base::internal::RunnableAdapter<void (AndroidDeviceManager::AndroidWebSocket::*)(const std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)>, void(AndroidDeviceManager::AndroidWebSocket*, const std::basic_string<char, std::char_traits<char>, std::allocator<char> >&), base::WeakPtr<AndroidDeviceManager::AndroidWebSocket>&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&>, base::internal::InvokeHelper<true, void, base::internal::RunnableAdapter<void (AndroidDeviceManager::AndroidWebSocket::*)(const std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)> >, void()>::Run 0x00007f56c40741c8 (chrome -callback.h:397 ) base::debug::TaskAnnotator::RunTask 0x00007f56c40605de (chrome -message_loop.cc:478 ) base::MessageLoop::RunTask 0x00007f56c4061f97 (chrome -message_loop.cc:487 ) base::MessageLoop::DoDelayedWork 0x00007f56c405b70e (chrome -message_pump_libevent.cc:227 ) base::MessagePumpLibevent::Run 0x00007f56c4990167 (chrome -run_loop.cc:35 ) base::RunLoop::Run 0x00007f56c8018c64 (chrome -chrome_browser_main.cc:1913 ) ChromeBrowserMainParts::MainMessageLoopRun 0x00007f56c6d0b7aa (chrome -browser_main_loop.cc:972 ) content::BrowserMainLoop::RunMainMessageLoopParts 0x00007f56c6b48224 (chrome -browser_main_runner.cc:165 ) content::BrowserMainRunnerImpl::Run 0x00007f56c6b48102 (chrome -browser_main.cc:46 ) content::BrowserMain 0x00007f56c493cb90 (chrome -content_main_runner.cc:788 ) content::ContentMainRunnerImpl::Run 0x00007f56c493b67a (chrome -content_main.cc:20 ) content::ContentMain 0x00007f56c45c7abe (chrome -chrome_main.cc:84 ) ChromeMain 0x00007f56c19eefb5 (libc-2.19.so -libc-start.c:292 ) __libc_start_main 0x00007f56c45c7917 (chrome + 0x01200917 ) _start
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 2 2016
Per triage: please take a look when you get a chance.
,
Jul 9 2016
This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 6 2017
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 9 2017
This no longer happens on TOT but it definitely doesn't work well. This should go to the folks who wrote the UI since it doesn't work with the keyboard.
,
Nov 29 2017
,
Mar 19 2018
,
Sep 15
Crash analysis has not encountered any reports for this bug for the past 90 days. We have added the label 'crash-BugNoRepro' Crash analysis will be automatically closing the bug in 6 days. If you do not want Crash analysis to automatically close the bug, please remove the label 'crash-BugNoRepro'. If you have any feedback on this feature, please contact pranavk@
,
Sep 29
Crash analysis has not encountered any reports for this bug for the past 90 days. Hence as per the comment 13 days ago, we are closing the bug and setting the status to WontFix. If you have any feedback on this feature, please contact pranavk@ |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mdub...@gmail.com
, May 20 2016