New issue
Advanced search Search tips

Issue 866788 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 866782
Owner:
Closed: Jul 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: [Settings] Browser gets crashed after clicking on 'USB devices' option.

Reported by db...@etouch.net, Jul 24

Issue description

Chrome version : 70.0.3501.0 (Official Build) 5437941df764183b1776e37da065505ad660f1c0-refs/branch-heads/3501@{#1}(32/64-bit) 
OS: Windows (7,8,8.1,10)

What steps will reproduce the problem?
(1) Fresh Launch chrome, navigate to chrome://settings/content page.
(2) Clcik on 'USB devices' option and observe.

Actual  : Browser gets crashed after clicking on 'USB devices' option 

Expected: Browser should not get crashed after clicking on 'USB devices' option.

This is a regression issue broken in ‘M-70’ and will soon provide other info.
Good build: 70.0.3500.0
Bad build: 70.0.3501.0

Uploaded Crash Report ID 73ba281175df0b48 (Local Crash ID: 27d225b5-08b2-41b7-9538-27cd2d15cdb3)
 
Expected_Crash.mp4
289 KB View Download
Labels: Stability-Crash HasTestcase hasbisect
Owner: proberge@chromium.org
Status: Assigned (was: Unconfirmed)
Update:

Unable to provide bisect using per-revision script since getting error while bisecting, hence re-bisected with old script: 

Narrow Bisect info : 

https://chromium.googlesource.com/chromium/src/+log/f8ffab5d79243cb7de978d17669e8decdb9141df..05d77a1fbd1e5c3aa15468e0c4ea833fe67a9b9a?pretty=fuller&n=10000

Suspect: r577346 ?

@proberge: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Note: Issue is Windows OS specific and is not reproducible on Mac and Linux OS.

Thank You!
Cc: reillyg@chromium.org
Stack trace for the crash id:
-----------------------------
Thread 49 (id: 0x11dc) CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0x00000010 ] MAGIC SIGNATURE THREAD
Stack Quality100%Show frame trust levels
0x00007ffbaa7bb365	(chrome.dll -core.c:1339 )	libusb_close
0x00007ffbaac876d3	(chrome.dll -scoped_libusb_device_handle.cc:28 )	device::ScopedLibusbDeviceHandle::Reset()
0x00007ffbaac87690	(chrome.dll -scoped_libusb_device_handle.cc:24 )	device::ScopedLibusbDeviceHandle::~ScopedLibusbDeviceHandle()
0x00007ffbaa7bde3c	(chrome.dll -usb_device_impl.cc:119 )	device::UsbDeviceImpl::OpenOnBlockingThread(base::OnceCallback<void >,scoped_refptr<base::TaskRunner>,scoped_refptr<base::SequencedTaskRunner>)
0x00007ffbaa7be040	(chrome.dll -bind_internal.h:649 )	base::internal::Invoker<base::internal::BindState<void (device::UsbDeviceImpl::*)(base::OnceCallback<void (scoped_refptr<device::UsbDeviceHandle>)>, scoped_refptr<base::TaskRunner>, scoped_refptr<base::SequencedTaskRunner>),scoped_refptr<device::UsbDeviceImpl>,base::OnceCallback<void (scoped_refptr<device::UsbDeviceHandle>)>,scoped_refptr<base::SingleThreadTaskRunner>,scoped_refptr<base::SequencedTaskRunner> >,void ()>::RunOnce
0x00007ffba8a74beb	(chrome.dll -task_annotator.cc:101 )	base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask *)
0x00007ffba8af8e3d	(chrome.dll -task_tracker.cc:529 )	base::internal::TaskTracker::RunOrSkipTask(base::internal::Task,base::internal::Sequence *,bool)
0x00007ffba8af8925	(chrome.dll -task_tracker.cc:404 )	base::internal::TaskTracker::RunAndPopNextTask(scoped_refptr<base::internal::Sequence>,base::internal::CanScheduleSequenceObserver *)
0x00007ffba8af7671	(chrome.dll -scheduler_worker.cc:329 )	base::internal::SchedulerWorker::RunWorker()
0x00007ffba8af72ef	(chrome.dll -scheduler_worker.cc:224 )	base::internal::SchedulerWorker::RunPooledWorker()
0x00007ffba9c4ccb3	(chrome.dll -platform_thread_win.cc:91 )	base::`anonymous namespace'::ThreadFunc
0x00007ffbd8ad13d1	(KERNEL32.dll + 0x000013d1 )	BaseThreadInitThunk
0x00007ffbda9054f3	(ntdll.dll + 0x000154f3 )	RtlUserThreadStart

Seems this stack trace is similar to  issue 866782  but reproduce steps are different.

@Proberage / reillyg : Could you please look into the issue.

Thank You!
Actual_Crash.mp4
268 KB View Download
Owner: reillyg@chromium.org
Thanks for the bug report. However, r577346 is not responsible. Re-assigning to reillyg who recently touched UsbDeviceImpl code.
Mergedinto: 866782
Status: Duplicate (was: Assigned)

Sign in to add a comment