New issue
Advanced search Search tips

Issue 908680 link

Starred by 4 users
Status: Duplicate
Merged: issue 907868
Owner:
jkardatzke@chromium.org
Closed: Nov 28
Cc:
tbuck...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Android Studio help window can cause a Chrome crash

Project Member Reported by jkardatzke@chromium.org, Nov 27 
Chrome OS 11297.0.0

Install Crostini, then Android Studio. Accept all the defaults and create a new project, just accept all the default settings.

Go to Help->Find Action. Type in 'resource file', then double click on the 'New Resource File' line and you will get either a crash or a hang.

For a hang the CPU usage of crosvm is pegged at 300% and chrome at 100% (renderer process).  messages just complains about the browser hang, but in the UI log we have this:

[16663:16663:1126/164702.196639:ERROR:gles2_cmd_decoder.cc(17747)] [.BrowserCompositor-0x1c9eafd20000]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[16663:16663:1126/164702.197028:ERROR:gles2_cmd_decoder.cc(10302)] [.BrowserCompositor-0x1c9eafd20000]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

for the crash, I had this both times:

tcmalloc: large alloc 1073741824 bytes == 0x12767f305000 @  0x58bf17140d0b 0x58bf16f7a090 0x58bf17028300 0x58bf1702802e 0x58bf172ee9c6 0x58bf1e61382c 0x58bf1b83e078 0x58bf1e6101e2 0x58bf1b067eae 0x58bf1b0677ea 0x58bf1e485416 0x58bf1e485a71 0x58bf1c7c7e46 0x58bf1b06aba3 0x58bf17b109c6 0x58bf17b10aad 0x58bf1b05b6c2 0x58bf1b2823fa 0x58bf17028d25 0x58bf1a19cfe7 0x58bf1a19d976 0x58bf17028511 0x58bf1a1c0364 0x58bf19d41420 0x58bf1800aae0 0x58bf1800e532 0x58bf18004236 0x58bf19d2fefb 0x58bf19d37b5a 0x58bf17133c7f 0x7eb9392cfa94
[23274:23274:1126/165933.892950:FATAL:memory_linux.cc(42)] Out of memory.

Comment 1 by jkardatzke@chromium.org, Nov 28 

Running a debug build of Chrome causes a DCHECK here when it normally would have crashed in non-debug mode:

[8790:8790:1127/163929.279814:FATAL:observer_list.h(271)] Check failed: false. Observers can only be added once!
#0 0x55e8ba5ac4f8 base::debug::StackTrace::StackTrace()
#1 0x55e8ba33686c base::debug::StackTrace::StackTrace()
#2 0x55e8ba37f8ca logging::LogMessage::~LogMessage()
#3 0x55e8be114c1f base::ObserverList<>::AddObserver()
#4 0x55e8be10f31f aura::Window::AddObserver()
#5 0x55e8b518aa36 exo::ShellSurfaceBase::SetParentWindow()
#6 0x55e8b517f423 exo::ShellSurface::SetParent()
#7 0x55e8b51cb387 exo::wayland::(anonymous namespace)::WaylandToplevel::SetParent()
#8 0x55e8b51caeb9 exo::wayland::(anonymous namespace)::xdg_toplevel_v6_set_parent()
#9 0x7af421937ca4 ffi_call_unix64
#10 0x7af4219373ab ffi_call
#11 0x55e8c24d663e wl_closure_invoke
#12 0x55e8c24d15c7 wl_client_connection_data
#13 0x55e8c24cf8c7 wl_event_source_fd_dispatch
#14 0x55e8c24d04de wl_event_loop_dispatch
#15 0x55e8b5198540 exo::wayland::Server::Dispatch()
#16 0x55e8b51142c5 ash::WaylandServerController::WaylandWatcher::OnFileCanReadWithoutBlocking()
#17 0x55e8ba5f4c7e base::MessagePumpLibevent::FdWatchController::OnFileCanReadWithoutBlocking()
#18 0x55e8ba5f648c base::MessagePumpLibevent::OnLibeventNotification()
#19 0x55e8ba65318b event_process_active
#20 0x55e8ba652724 event_base_loop
#21 0x55e8ba5f6608 base::MessagePumpLibevent::Run()
#22 0x55e8ba399bf3 base::MessageLoopImpl::Run()
#23 0x55e8ba4246ad base::RunLoop::Run()
#24 0x55e8b936cf33 ChromeBrowserMainParts::MainMessageLoopRun()
#25 0x55e8b2a883c1 content::BrowserMainLoop::RunMainMessageLoopParts()
#26 0x55e8b2a90f70 content::BrowserMainRunnerImpl::Run()
#27 0x55e8b2a7b48b content::BrowserMain()
#28 0x55e8b933d287 content::RunBrowserProcessMain()
#29 0x55e8b9340040 content::ContentMainRunnerImpl::Run()
#30 0x55e8b933471c content::ContentServiceManagerMainDelegate::RunEmbedderProcess()
#31 0x55e8b9356f4a service_manager::Main()
#32 0x55e8b933ac13 content::ContentMain()
#33 0x55e8aeed9f78 ChromeMain
#34 0x55e8aeed9e62 main
#35 0x7af4207d2a94 __libc_start_main
#36 0x55e8aeed9d19 _start

Comment 2 by jkardatzke@chromium.org, Nov 28

Status: Started (was: Assigned)

Comment 3 by jkardatzke@chromium.org, Nov 28

Mergedinto: 907868
Status: Duplicate (was: Started)
I'm merging this back into the VSCode bug. Now that I've figured out what it is and have a fix, I'm pretty sure it's the same problem.
►

Sign in to add a comment