Since posting it's done it twice. I never killed the first tab, so now the task manager is showing it locking 2 of my 8 CPU cores.

In both cases the tab became unresponsive while I was tying messages in Messenger on Facebook.com. 

Deleted: Capture fb2.PNG 10.1 KB

	Capture fb2.PNG 10.1 KB View Download

I saw you change the status of this to needing triage, so for fun I thought I wonder if I can trigger it. Just now I:

1) Opened Facebook in a new tab
2) Opened four random chat windows
3) Clicked between the chat windows approx 5 times and it locked up

Additionally, in the time it's taken me to type this out, I hadn't closed the tab. You can see the memory usage increase by about 200+ MB, so it definitely seems to be a leak. 

Deleted: Capture fb3.PNG 6.2 KB

	Capture fb3.PNG 6.2 KB View Download

Deleted: Capture fb4.PNG 6.3 KB

	Capture fb4.PNG 6.3 KB View Download

Additionally, I wasn't originally going to post this as I wasn't sure it was related, but when I posted the double tab screenshot earlier I actually left them open. A few minutes later my screens flashed black and my system became unresponsive (both locally and over the network). It was a hard crash and I had to reboot. 

Now I'm thinking it might be related. As I type this just a few seconds after posting the above, it's already to 900 MB of memory usage (update: see screenshots, it grew as I typed). My computer build is custom and stable, and since it was upgraded 2+ years ago has never had a hard crash until now. So perhaps this memory leak also includes some sort of memory access issue that is trickling up to the OS level. 

I'm a software dev so happy to help triage/debug as needed. 

Deleted: Capture fb5.PNG 6.8 KB

	Capture fb5.PNG 6.8 KB View Download

Deleted: Capture fb6.PNG 6.7 KB

	Capture fb6.PNG 6.7 KB View Download

Tested the issue on windows 10 & windows 7 using latest chrome stable M59 #59.0.3071.86 and issue is no reproduced with below steps :

1. Logged into facebook and launched messenger and opened many chat windows and chatted for few mins and left the facebook for 45mins and when checked after it .. no chrome freeze or tab crash or unresponsive pages are seen ..

@c.cicchitelli-- Could you please update your chrome to latest stable and try in fresh chrome profile without any extensions and flags enabled and update us with your observations.

Thnaks!

I'll echo the request to try with no extensions installed. An easy way to do this is to try it in an Incognito tab. Does the issue reproduce that way?

I just updated to the new release. Interestingly have not had a recurrence yet since the fb6 screenshot above. I don't remember exactly but I would say this started happening about two weeks ago. I first tweeted about it May 31st. For extensions, I have only four: AdBlock Plus, MailTrack for Gmail, Video Speed Controller, and Resolution Test. I'm running FB now in an incognito tab and will report back... 

Thank you for providing more feedback. Adding requester "hdodda@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

Well that didn't take long. Attached... 

I had opened the tab before I typed the above message. After opening, I opened 6 chat windows. Clicked between several of them randomly. In a couple, I had typed and erased random text (not much, just a few characters). Came here, typed the message above, switched back to that tab, clicked in one chat box it worked, then tried to another and it was locked. In the time it's taken me to write the above paragraph I'm now at 750 MB memory consumption on that tab. 

Deleted: Capture fb incognito.PNG 8.1 KB

	Capture fb incognito.PNG 8.1 KB View Download

Note: for the first time Chrome noticed the page has become unresponsive and offered to kill it for me. I clicked Kill and it successfully killed it. Previously I had to manually kill the tabs via Chrome's Task Manager. 

@c.cicchitelli-- Could you please provide us the crash id from chrome://crashes ,that would help us in traiging better.

Thanks!

Well as mentioned above it's not generating crash logs, BUT I just double checked the most one that did generate the "kill page?" message, and sure enough it does have a crash log. It happened since then and did not leave a log, so we got 1 log for 20+ crashes. 

4e8298cc-f2f2-4f15-b1f0-f259db23d314

Thank you for providing more feedback. Adding requester "hdodda@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

In my daily use today, the first two of my Facebook tabs used (with Messenger in use) locked up. I left them open to see if they'd generate a crash log. After a few minutes of being frozen, they then went to a white (blank page). A few minutes later, Chrome as a whole crashed due to a memory error (attached). 

Note that while the restore pages function did work, no crash log was generated.

I think it's clear now that Chrome has a memory leak here, and it's not only affecting the Browser stability, but the OS stability as well (see above). Hopefully we can upgrade the priority on this bug...

Thanks!

Deleted: chrome memory crash.PNG 26.9 KB

	chrome memory crash.PNG 26.9 KB View Download

Any update guys? This just happened again (as it has many times since my last message), but this time it cost me as a long message I was typing is lost. So now I'm pretty frustrated.... 

Actually two messages, if you include the post reply I was also typing. 

@c.cicchitelli -- Could you please update your stable version to latest M59 #59.0.3071.104 and check ,if you can still reproduce the issue , please provide us the crash id.Please refer to attached  screenshot.

Thanks!

Deleted: crashes.png 25.4 KB

	crashes.png 25.4 KB View Download

Don't see any reason this is related to Performance-Memory

I can confirm it's happened with 3071.109. There was actually a few days before I received the message on Jun 19 that I thought it had resolved itself, but it has come back 3 times since the update. 

I also sometimes get WebGL crashed/needs a refresh warnings when using Facebook/Messenger. Perhaps that is a correlation and not random? 

I also want to confirm I've had zero issues with any other website, or with Facebook itself when not using Messenger. 

Thank you for providing more feedback. Adding requester "hdodda@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

If it helps:
I tried switching to beta and the issue is still present.
It's also heppening even with all the graphics flags turned off (hw acceleration and 2d ones)

Hello, 
I am also having this issue and it was way worse on Windows 10 where the ram gets filled up to the max and it crashes, with windows 7 I could just kill the process.

It happens when you click on the chat box in facebook randomly, hope it gets fixed asap.

Can you please run the repro while recording a trace?

https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs

Please attach the trace and we can possibly look into why it's happening.

I've updated to the latest and this continues to happen. I don't have a trace yet though. 

I will say I'm 99% confident this is from WebGL, just based on correlations between issues and warnings I'm seeing. 

Thank you for providing more feedback. Adding requester "ajha@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

Ken - do you have any ideas?

Sorry, I don't. On a dual-GPU MacBook Pro, going to www.facebook.com, clicking the Messages icon at the top, opening a few chat panels (over the Facebook feed, not from www.facebook.com/messages), and typing some text into them, switching among them, deleting that text, etc. does not create a WebGL rendering context. (My system doesn't switch from the integrated to the discrete GPU, which would happen if a WebGL rendering context were created.)

Capturing a trace is the next step toward a diagnosis.

Please provide about:gpu from an affected system. Here is mine.

Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Hardware accelerated
Rasterization: Hardware accelerated
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
add_and_true_to_loop_condition
adjust_src_dst_region_for_blitframebuffer
decode_encode_srgb_for_generatemipmap
disable_framebuffer_cmaa
disable_multimonitor_multisampling
disable_webgl_rgb_multisampling_usage
emulate_abs_int_function
get_frag_data_info_bug
init_two_cube_map_levels_before_copyteximage
msaa_is_slow
pack_parameters_workaround_with_pack_buffer
rebind_transform_feedback_before_resume
regenerate_struct_names
remove_invariant_and_centroid_for_essl3
rewrite_texelfetchoffset_to_texelfetch
scalarize_vec_and_mat_constructor_args
set_zero_level_before_generating_mipmap
unfold_short_circuit_as_ternary_operation
unpack_alignment_workaround_with_unpack_buffer
unpack_image_height_workaround_with_unpack_buffer
use_intermediary_for_copy_texture_image
use_unused_standard_shared_blocks
avoid_stencil_buffers
Problems Detected
Multisampling is buggy on OSX when multiple monitors are connected: 237931
Applied Workarounds: disable_multimonitor_multisampling
Unfold short circuit on Mac OS X: 307751
Applied Workarounds: unfold_short_circuit_as_ternary_operation
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Mac drivers handle struct scopes incorrectly: 403957
Applied Workarounds: regenerate_struct_names
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
glGenerateMipmap fails if the zero texture level is not set on some Mac drivers: 560499
Applied Workarounds: set_zero_level_before_generating_mipmap
Pack parameters work incorrectly with pack buffer bound: 563714
Applied Workarounds: pack_parameters_workaround_with_pack_buffer
Alignment works incorrectly with unpack buffer bound: 563714
Applied Workarounds: unpack_alignment_workaround_with_unpack_buffer
copyTexImage2D fails when reading from IOSurface on multiple GPU types.: 581777
Applied Workarounds: use_intermediary_for_copy_texture_image
Multisample renderbuffers with format GL_RGB8 have performance issues on Intel GPUs.: 607130
Applied Workarounds: disable_webgl_rgb_multisampling_usage
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
glGetFragData{Location|Index} works incorrectly on Max: 638340
Applied Workarounds: get_frag_data_info_bug
glResumeTransformFeedback works incorrectly on Intel GPUs: 638514
Applied Workarounds: rebind_transform_feedback_before_resume
Result of abs(i) where i is an integer in vertex shader is wrong: 642227
Applied Workarounds: emulate_abs_int_function
Rewrite texelFetchOffset to texelFetch for Intel Mac: 642605
Applied Workarounds: rewrite_texelfetchoffset_to_texelfetch
Rewrite condition in for and while loops for Intel Mac: 644669
Applied Workarounds: add_and_true_to_loop_condition
Decode and encode before generateMipmap for srgb format textures on macosx: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Init first two levels before CopyTexImage2D for cube map texture on Intel Mac 10.12: 648197
Applied Workarounds: init_two_cube_map_levels_before_copyteximage
Insert statements to reference all members in unused std140/shared blocks on Mac: 618464
Applied Workarounds: use_unused_standard_shared_blocks
Tex(Sub)Image3D performs incorrectly when uploading from unpack buffer with GL_UNPACK_IMAGE_HEIGHT greater than zero on Intel Macs: 654258
Applied Workarounds: unpack_image_height_workaround_with_unpack_buffer
adjust src/dst region if blitting pixels outside read framebuffer on Mac: 644740
Applied Workarounds: adjust_src_dst_region_for_blitframebuffer
Mac driver GL 4.1 requires invariant and centroid to match between shaders: 639760, 641129
Applied Workarounds: remove_invariant_and_centroid_for_essl3
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Certain Apple devices leak stencil buffers: 713854
Applied Workarounds: avoid_stencil_buffers
Version Information
Data exported	7/6/2017, 5:45:40 PM
Chrome version	Chrome/59.0.3071.115
Operating system	Mac OS X 10.12.5
Software rendering list version	13.8
Driver bug list version	10.102
ANGLE commit id	a9042d3c1952
2D graphics backend	Skia/59 ef6f9c65527412ec4057ea0551f2e051beb94d32
Command Line Args	Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --flag-switches-end
Driver Information
Initialization time	53
In-process GPU	false
Passthrough Command Decoder	false
Supports overlays	false
Sandboxed	true
GPU0	VENDOR = 0x10de, DEVICE= 0x0fe9
GPU1	VENDOR = 0x8086, DEVICE= 0x0d26 *ACTIVE*
Optimus	true
Optimus	true
AMD switchable	false
Driver vendor	
Driver version	10.25.13
Driver date	
Pixel shader version	4.10
Vertex shader version	4.10
Max. MSAA samples	8
Machine model name	MacBookPro
Machine model version	11.3
GL_VENDOR	Intel Inc.
GL_RENDERER	Intel Iris Pro OpenGL Engine
GL_VERSION	4.1 INTEL-10.25.13
GL_EXTENSIONS	GL_ARB_blend_func_extended GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader5 GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_occlusion_query2 GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_shading_language_include GL_ARB_tessellation_shader GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_vertex_attrib_64bit GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_EXT_texture_sRGB_decode GL_APPLE_client_storage GL_APPLE_container_object_shareable GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_texture_range GL_ATI_texture_mirror_once GL_NV_texture_barrier
Disabled Extensions	GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
Window system binding vendor	
Window system binding version	
Window system binding extensions	
Direct rendering	Yes
Reset notification strategy	0x0000
GPU process crash count	0
Compositor Information
Tile Update Mode	Zero-copy
Partial Raster	Enabled
GpuMemoryBuffers Status
ATC	Software only
ATCIA	Software only
DXT1	Software only
DXT5	Software only
ETC1	Software only
R_8	GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
RG_88	Software only
BGR_565	Software only
RGBA_4444	Software only
RGBX_8888	Software only
RGBA_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE
BGRX_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE
BGRA_8888	GPU_READ, SCANOUT, SCANOUT_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
RGBA_F16	GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
YVU_420	Software only
YUV_420_BIPLANAR	GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT
UYVY_422	GPU_READ_CPU_READ_WRITE, GPU_READ_CPU_READ_WRITE_PERSISTENT

I am working on the trace, but I can confirm that in usage the last few days, on many occasions I've gotten the WebGL crashed popup bar at the very instant a incoming chat window pops up in the Facebook page. This is on a Windows 10 PC.

Explicitly adding Ken in case he has seen what's described in comment #29 before.

Sorry, I have not. We just did a test and there was no "Rats" infobar upon incoming message with Chrome Stable on Windows 10. Here is about:gpu from my workstation.

Submitter, I suggest you try running Chrome from the command line explicitly with for example:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --user-data-dir=C:\Users\[your username]\t1

Log in to Facebook, and see whether the behavior reproduces. If not, it's a problem with one of your extensions or something else in your user profile.


Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
decode_encode_srgb_for_generatemipmap
disable_accelerated_vpx_decode
disable_discard_framebuffer
disable_dxgi_zero_copy_video
disable_framebuffer_cmaa
exit_on_context_lost
force_cube_complete
scalarize_vec_and_mat_constructor_args
texsubimage_faster_than_teximage
Problems Detected
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
TexSubImage is faster for full uploads on ANGLE
Applied Workarounds: texsubimage_faster_than_teximage
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Decode and Encode before generateMipmap for srgb format textures on Windows: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Zero-copy DXGI video hangs or displays incorrect colors on AMD drivers: 623029
Applied Workarounds: disable_dxgi_zero_copy_video
VPx decoding isn't supported before Windows 10 anniversary update.: 616318
Applied Workarounds: disable_accelerated_vpx_decode
Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: rasterization
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Version Information
Data exported	7/13/2017, 2:48:12 PM
Chrome version	Chrome/59.0.3071.115
Operating system	Windows NT 10.0.10586
Software rendering list version	13.8
Driver bug list version	10.102
ANGLE commit id	a9042d3c1952
2D graphics backend	Skia/59 ef6f9c65527412ec4057ea0551f2e051beb94d32
Command Line Args	Files (x86)\Google\Chrome\Application\chrome.exe" --user-data-dir="C:\Users\kbr\tmp\t1" --flag-switches-begin --flag-switches-end
Driver Information
Initialization time	608
In-process GPU	false
Passthrough Command Decoder	false
Supports overlays	false
Sandboxed	false
GPU0	VENDOR = 0x1002, DEVICE= 0x683d
Optimus	false
Optimus	false
AMD switchable	false
Desktop compositing	Aero Glass
Diagonal Monitor Size of \\.\DISPLAY1	29.7"
Driver vendor	Advanced Micro Devices, Inc.
Driver version	21.19.519.2
Driver date	2-10-2017
Pixel shader version	5.0
Vertex shader version	5.0
Max. MSAA samples	8
Machine model name	
Machine model version	
GL_VENDOR	Google Inc.
GL_RENDERER	ANGLE (AMD Radeon R7 200 Series Direct3D11 vs_5_0 ps_5_0)
GL_VERSION	OpenGL ES 3.0 (ANGLE 2.1.0.a9042d3c1952)
GL_EXTENSIONS	GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_robust_resource_initialization GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_norm16 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object
Disabled Extensions	GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
Window system binding vendor	Google Inc. (adapter LUID: 00000000000150c8)
Window system binding version	1.4 (ANGLE 2.1.0.a9042d3c1952)
Window system binding extensions	EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture_nv12 EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_create_context_robust_resource_initialization
Direct rendering	Yes
Reset notification strategy	0x8252
GPU process crash count	0
Compositor Information
Tile Update Mode	One-copy
Partial Raster	Enabled
GpuMemoryBuffers Status
ATC	Software only
ATCIA	Software only
DXT1	Software only
DXT5	Software only
ETC1	Software only
R_8	Software only
RG_88	Software only
BGR_565	Software only
RGBA_4444	Software only
RGBX_8888	Software only
RGBA_8888	Software only
BGRX_8888	Software only
BGRA_8888	Software only
RGBA_F16	Software only
YVU_420	Software only
YUV_420_BIPLANAR	Software only
UYVY_422	Software only

Hey c.cicchitelli@ - thanks for sticking with us. Bugs like these are difficult to investigate and we're trying to reproduce what you're experiencing on our side so that we won't have to do so much back and forth, so the fact that you've been so helpful in providing information is helping us. 

That said, if you're still having these issues and can attach a trace, that would be very helpful. Until then, this bug will sit in limbo. If you're not experiencing the issue anymore, we should close this bug.

Another option, c.cicchitelli@, is to record what is called an ETW trace. Sometimes these are easier to record than a chrome://tracing trace. Instructions on recording an ETW trace can be found here:

https://randomascii.wordpress.com/2015/09/01/xperf-basics-recording-a-trace-the-ultimate-easy-way/

You can leave ETW tracing running 24x7 and then when you get the hang just leave the browser running for 5-10 seconds and click "Save Trace Buffers" in UIforETW. If you can then share the resulting .etl file (from documents\etwtraces) on Google Drive/Drop Box/whatever then I can analyze it.

Or, a chrome://tracing trace. But we need one of them to understand what is going on with your machine.

Also, if your theory is correct that this is a WebGL issue then seeing the contents of the about:gpu page from your machine is crucial, since this bug clearly doesn't happen on most machines.

c.cicchitelli@

Could you please respond as per C#33.
Thank you.!

All - I'm no longer able to replicate this behavior and am no longer facing crashes. I'll update if that changes. Thanks! 

Thank you for providing more feedback. Adding requester "jmukthavaram@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

Thanks for the response.
As per C#36,marking this issue as Wontfix. Please feel free to find a new chrome issue if you find any.