Hello, thank you for your report.

If you have a consistently reproducible example, please add details to a ticket.

http://www.chromium.org/Home/chromium-security/reporting-security-bugs

https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug

Thanks!

Hello,
I checked /home/mcan/.config/google-chrome/Crash Reports is empty but crash continues.

Crash (Debian 8) Step to Step:
1- Open any web site inspect element
2- another div select
3- selected div drag
4- chrome crash and system logout

if you want i record screen ?

Thank you for providing more feedback. Adding requester "pennymac@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Could you confirm whether you're running 32 or 64-bit Debian 8?

Is crash reporting enabled on your system?

"enable crash reporting in Google Chrome's settings: go to chrome://chrome/settings, click "Show advanced settings..." and in the Privacy section select select "Automatically send usage statistics and crash reports to Google""

Then if you restart and repro the crash again, see if there is a crash listed under chrome://crashes.

I using Debian 8 64-bit and i opened error reporting.

Errors;
report_id:3dfc3dc400000000
report_id:fe6d24cc00000000

Thank you for providing more feedback. Adding requester "pennymac@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Sounds like the GPU process isn't happy with the particular graphics drivers. Assigning to krb@, can you find an appropriate owner? Thanks.

I try another computer and I got same error again. Computer that have different features

The GPU setup on this computer is strange. The crash report contains:

device id	0x10de 0x1292GK208M [GeForce GT 740M]
vendor id	0x10deNVIDIA Corporation
driver	10.3.2
gl vendor	Intel Open Source Technology Center
gl renderer	Mesa DRI Intel(R) Haswell Mobile

So the system thinks it contains an NVIDIA GPU, but it's running an old version of Mesa on a (presumably integrated) Intel GPU.

You can launch chrome with --disable-gpu on the command line to work around this problem.

I'm not sure what kind of blacklist entry is needed to catch this case. Perhaps this one would catch it if the Mesa version were increased to for example 10.4:

https://chromium.googlesource.com/chromium/src/+/master/gpu/config/software_rendering_list_json.cc#368

Even Mesa 10.3 is pretty old, and unsupported by Intel at this point.

I tried --disable-gpu but it did not working again 

Please copy/paste the contents of about:gpu (plain text please) from Chrome when you've launched it with the --disable-gpu command line. Thanks.

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Multiple Raster Threads: Unavailable
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
WebGL: Unavailable
Driver Bug Workarounds
clear_uniforms_before_first_program_use
count_all_in_varyings_packing
disable_msaa_on_non_webgl_contexts
disable_post_sub_buffers_for_onscreen_surfaces
disable_texture_storage
scalarize_vec_and_mat_constructor_args
Problems Detected
GPU process was unable to boot: GPU access is disabled through commandline switch --disable-gpu.
Disabled Features: all
Accelerated 2d canvas is unstable in Linux at the moment
Disabled Features: accelerated_2d_canvas
Accelerated video decode is unavailable on Linux: 137247
Disabled Features: accelerated_video_decode
EXT_occlusion_query appears to be buggy with Intel GPUs on Linux
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Mesa drivers in Linux handle varyings without static use incorrectly: 333885
Applied Workarounds: count_all_in_varyings_packing
Disable partial swaps on linux drivers: 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Linux Mesa drivers crash on glTexSubImage2D() to texture storage bound to FBO: 521904
Applied Workarounds: disable_texture_storage
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: disable_msaa_on_non_webgl_contexts
Timer queries crash on Intel GPUs on Linux: 540543, 576991
Accelerated rasterization has been disabled, either via about:flags or command line.
Disabled Features: rasterization
GpuMemoryBuffer Status
ATC	Software only
ATCIA	Software only
DXT1	Software only
DXT5	Software only
ETC1	Software only
R_8	Software only
RGBA_4444	Software only
RGBX_8888	Software only
RGBA_8888	Software only
BGRX_8888	Software only
BGRA_8888	Software only
YUV_420	Software only
YUV_420_BIPLANAR	Software only
UYVY_422	Software only
Version Information
Data exported	15.04.2016 08:36:44
Chrome version	Chrome/49.0.2623.112
Operating system	Linux 3.16.0-4-amd64
Software rendering list version	10.17
Driver bug list version	8.46
ANGLE commit id	4e9536d0f612
2D graphics backend	Skia
Command Line Args	--window-depth=24 --flag-switches-begin --flag-switches-end --disable-gpu --window-depth=24 --flag-switches-begin --flag-switches-end
Driver Information
Initialization time	0
In-process GPU	true
Sandboxed	false
GPU0	VENDOR = 0x10de, DEVICE= 0x1292
GPU1	VENDOR = 0x8086, DEVICE= 0x0416 *ACTIVE*
Optimus	true
AMD switchable	false
Driver vendor	Mesa
Driver version	10.3.2
Driver date	
Pixel shader version	
Vertex shader version	
Max. MSAA samples	
Machine model name	
Machine model version	
GL_VENDOR	Intel Open Source Technology Center
GL_RENDERER	Mesa DRI Intel(R) Haswell Mobile
GL_VERSION	3.0 Mesa 10.3.2
GL_EXTENSIONS	
Disabled Extensions	GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_timer_query GL_EXT_timer_query
Window system binding vendor	
Window system binding version	
Window system binding extensions	
Window manager	GNOME Shell
XDG_CURRENT_DESKTOP	GNOME
GDMSESSION	default
Compositing manager	Yes
Direct rendering	Yes
Reset notification strategy	0x0000
GPU process crash count	0

Doesn't look like it's new to M50: https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.magic_signature_1.name%3D%27gpu%3A%3Agles2%3A%3AGLES2DecoderImpl%3A%3AInitialize%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion,gpuvendorid,gpudriverversion

Happens with every DRI driver across many versions. There are some ChromeOS reports in there too.