New issue
Advanced search Search tips

Issue 668977 link

Starred by 5 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Browser freezes when using chrome.debugger Input.dispatchMouseEvent to simulate drag on images

Reported by pda...@gmail.com, Nov 28 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce the problem:
1. attach a debugger to any tab using the chrome.debugger api
2. send mousePressed with Button=0 clickCount=1
 over any image on the website using Input.dispatchMouseEvent
3. send mouseMoved with Button=0 clickCount=1 to anywhere else on the screen

What is the expected behavior?

What went wrong?
the entire tab freezes and stops doing anything (updating animations, for example)

Did this work before? No 

Chrome version: 57.0.2931.0  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

I'm using the canary version but this is happening on stable versions as well
 

Comment 1 by ajha@chromium.org, Nov 28 2016

Labels: M-57

Comment 2 by rbyers@chromium.org, Nov 28 2016

Components: Platform>DevTools
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 4 by pda...@gmail.com, Nov 29 2016

I've made a simple extension that reproduces the bug

just load the extension
navigate to test.html
and press the browser_action

please note that as soon as the mouse moves inside the chrome window it will unfreeze. so make sure not to move the mouse after pressing the browser_action.
chromiumbug.7z
893 bytes Download
Labels: Hotlist-Polish

Comment 6 by clu...@gmail.com, Jul 11 2017

 I'm running to a Chrome crash issue on OSX when I invoke Input.dispatchMouseEvent on the headless Chrome. I have tried it on stable chrome v59 and canary. Both will result in crash consistently.

The input that I passed in seems to be in the correct format:

{
    button: 'left',
    clickCount: 1,
    type: 'mousePressed',
    x: (some number),
    y: (some number)
}

See following printout in OSX bug report. I can provide more if need to.

Process:               Google Chrome [41632]
Path:                  /Users/USER/*/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier:            com.google.Chrome
Version:               59.0.3071.115 (3071.115)
Code Type:             X86-64 (Native)
Parent Process:        node [41630]
Responsible:           Google Chrome [41632]
User ID:               502

Date/Time:             2017-07-10 21:58:23.024 -0700
OS Version:            Mac OS X 10.12.5 (16F73)
Report Version:        12
Anonymous UUID:        EA02703F-27EB-D386-9BC9-F146A4BDA2C3

Sleep/Wake UUID:       CDBAC4BA-741C-4682-B203-8F62CF5EB756

Time Awake Since Boot: 79000 seconds
Time Since Wake:       8300 seconds

System Integrity Protection: enabled

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [0]

Application Specific Information:
Crashing on exception: -[HeadlessShellCrApplication setHandlingSendEvent:]: unrecognized selector sent to instance 0x7fec88f072d0
Labels: Proj-Headless Needs-Feedback
> Crashing on exception: -[HeadlessShellCrApplication setHandlingSendEvent:]: unrecognized selector sent to instance 0x7fec88f072d0
This line suggests you are using headless browser, aren't you?
Status: WontFix (was: Assigned)
Closing per lack of feedback.

Comment 9 by pda...@gmail.com, Oct 4 2017

the original report is on a non headless.

Sign in to add a comment