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

Issue 716082 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Segfault in ui::DeviceDataManagerX11::GetDataRange when double clicking in some textareas

Reported by w...@219design.com, Apr 27 2017

Issue description

Chrome Version       : 57.0.2987.98
OS Version: Debian 8.7 (jessie)
URLs (if applicable) : gmail.com
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 53:  OK
     IE 7/8/9:

What steps will reproduce the problem?
1. Go to gmail.com
2. Click in the reply area of an email
3. Double click anywhere in the textarea

What is the expected result?
Normal textarea stuff -- select a word

What happens instead of that?
Segfault

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36



 
chrome-gdb
8.1 KB View Download

Comment 1 by w...@219design.com, Apr 27 2017

Same behavior if all extensions are disabled.

It also happens when double clicking on the chrome://extensions page.

Comment 2 by w...@219design.com, Apr 27 2017

Does not happen on about:blank or chrome://version


Chromium	57.0.2987.98 (Developer Build) Built on 8.7, running on Debian 8.7 (64-bit)
Revision	a6a06b78087c9fdb4b12fe0ac1b87fdc10179f8b
OS	Linux 
JavaScript	V8 5.7.492.63
Flash	(Disabled)
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36
Command Line	/usr/lib/chromium/chromium --flag-switches-begin --flag-switches-end
Executable Path	/usr/lib/chromium/chromium
Profile Path	/home/wes/.config/chromium/Default

Comment 3 by w...@219design.com, Apr 27 2017

Also happens when double clicking on this exact page, inside or outside of the textarea (just trying to select a word in the bug report by double clicking) 

(The crash is coming from _inside the bug report_!!!)
Hi,

Can you navigate to chrome://crashes and provide the crash IDs of these crashes?

Comment 5 by w...@219design.com, Apr 27 2017

chrome://crashes shows "Crash reporting is not available in Chromium"

I don't use the G branded browser. Is there a way to generate the same crash report without contacting a G server?

If not, I can try installing the branded browser and trying to repeat it.

Comment 6 by w...@219design.com, May 3 2017

This crash also occurs sometimes when the rendering pauses after a click, and then I click again before rendering resumes.

What I mean by "the rendering pauses" is that I'll click on something that opens a modal dialog, and move the mouse. During that time the cursor remains pointer, even though I'm not hovering over anything. If I wait with the mouse in the same place the cursor returns to  default. But if I click *before* that time, chromium segfaults.

Comment 7 by w...@219design.com, May 3 2017

The crash occurs with the trackpad, and a USB mouse, but I can't duplicate it by tapping on the touch screen. I don't have to double click very fast.

I don't think Debian's chromium-dbg (57.0.2987.98-1~deb8u1) package has all the symbols, or at least running `chromium -g` doesn't let me inspect any locals with gdb. But from looking at the source, it's got to be either a) a null pointer dereference or b) deviceid is less than zero

https://chromium.googlesource.com/chromium/src/+/master/ui/events/devices/x11/device_data_manager_x11.cc#676

BTW I'm using the i3 window manager, if that might affect how the process receives events.

Comment 8 by w...@219design.com, May 4 2017

Here's what was happening as best I understand: I had a script in the background running setxkbmap every five seconds (a dumb hack). This causes i3 to reload its configuration which takes a few hundred milliseconds. During this time, the X input events are buffered. When the reload finishes, all the buffered X input events get dumped all at once.

After removing that background process, I can't reproduce the problem.

Cc: krajshree@chromium.org
Labels: Needs-Feedback
wes@ - As per comment #8, please confirm if the issue can be closed.

Thanks...!!

Comment 10 by w...@219design.com, Jul 24 2017

The crash no longer occurs for me
Project Member

Comment 11 by sheriffbot@chromium.org, Jul 24 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
As per C#8 & C#10,marking this issue as Wontfix.
Please feel free to file chrome issue if you find any.
Thanks..!

Sign in to add a comment