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

Issue 729534 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Tabs start to endlessly spin or show ow, snap tabs after a while

Reported by asheme...@gmail.com, Jun 5 2017

Issue description

UserAgent: Mozilla/5.0 (X11; FreeBSD amd64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Unsure as of yet. It seems the problem occurs after a while of browsing on JavaScript heavy pages.
2. Disabling GPU acceleration only postpones the inevitable.
3. 

What is the expected behavior?
No endlessly spinning tabs or ow, snap tabs.

What went wrong?
Tab will start to show the spinner, spinning, spinning, and never stopping. If you are lucky it will honour the close button at some point. Or you get the UI kill/wait dialog box if you are truly fortunate.

Crashed report ID: No, disabled on Chromium

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 11.1
Flash Version: 

This is FreeBSD 11-STABLE, currently at 11.1-PRERELEASE

Please see this bug report over at freebsd.org for more background from other individuals: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812 - in particular https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812#c24 which pinpoints some possible causes.
 
It would help if the issue tracker would support FreeBSD as an OS choice for properly filing. :)

Mandatory uname: FreeBSD dealer 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #7 r319368M: Thu Jun  1 08:01:01 CEST 2017     root@dealer:/usr/obj/usr/src/sys/DEALER  amd64

nvidia-driver-375.66 - native FreeBSD nvidia driver

When the endless spinning happens it seems to always spin counter-clockwise, but I need to verify this to be 100% certain.

When I use FreeBSD truss(1) and attach to the PID I see no system calls being triggered. If I select the tab and move the mouse over the canvas I do get mouse tracking events:

recvmsg(0x15,0x7fffdfdfc7f0,0x80)		 = 440 (0x1b8)
kevent(17,{ },0,{ },64,{ 0.000000000 })		 = 0 (0x0)
kevent(17,{ },0,{ },64,{ 0.000000000 })		 = 0 (0x0)
kevent(17,{ },0,{ 21,EVFILT_READ,0x0,0x0,0x130,0x81dc1c180 },64,0x0) = 1 (0x1)

Including chrome://gpu below:

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: Software only, hardware acceleration unavailable
VPx Video Decode: Software only, hardware acceleration unavailable
WebGL: Hardware accelerated
WebGL2: Hardware accelerated

Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_framebuffer_cmaa
scalarize_vec_and_mat_constructor_args

Problems Detected
Accelerated video decode is unavailable on Linux: 137247
Disabled Features: accelerated_video_decode
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
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
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	6/5/2017, 2:46:18 PM
Chrome version	Chrome/58.0.3029.110
Operating system	FreeBSD 11.1-PRERELEASE
Software rendering list version	12.20
Driver bug list version	9.36
ANGLE commit id	unknown hash
2D graphics backend	Skia/58 4c81ba6ba3a3270db809bf7d4c3bc782694a56a4
Command Line Args	--flag-switches-begin --flag-switches-end

Driver Information
Initialization time	0
In-process GPU	true
Passthrough Command Decoder	false
Sandboxed	false
GPU0	VENDOR = 0x0000, DEVICE= 0x0000
Optimus	false
Optimus	false
AMD switchable	false
Driver vendor	
Driver version	
Driver date	
Pixel shader version	
Vertex shader version	
Max. MSAA samples	
Machine model name	
Machine model version	
GL_VENDOR	
GL_RENDERER	
GL_VERSION	
GL_EXTENSIONS	
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	
Window manager	Xfwm4
XDG_CURRENT_DESKTOP	XFCE
Compositing manager	Yes
Direct rendering	Yes
Reset notification strategy	0x0000
GPU process crash count	0
System visual ID	0
RGBA visual ID	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
YVU_420	Software only
YUV_420_BIPLANAR	Software only
UYVY_422	Software only

Log Messages
[1090:467363840:0605/135010.205248:WARNING:x11_util.cc(1360)] : X error received: serial 46954, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:465657856:0605/140040.210314:WARNING:ipc_message_attachment_set.cc(49)] : MessageAttachmentSet destroyed with unconsumed attachments: 0/1
[1090:467363840:0605/140618.313001:WARNING:x11_util.cc(1360)] : X error received: serial 140050, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/140634.675794:WARNING:x11_util.cc(1360)] : X error received: serial 141803, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/140657.627375:WARNING:x11_util.cc(1360)] : X error received: serial 144174, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/140700.096069:WARNING:x11_util.cc(1360)] : X error received: serial 144486, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/140704.265761:WARNING:x11_util.cc(1360)] : X error received: serial 144971, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/141005.098135:WARNING:x11_util.cc(1360)] : X error received: serial 154149, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/141312.401559:WARNING:x11_util.cc(1360)] : X error received: serial 165952, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:465657856:0605/141710.278215:WARNING:ipc_message_attachment_set.cc(49)] : MessageAttachmentSet destroyed with unconsumed attachments: 0/1
[1090:467363840:0605/142235.116605:WARNING:x11_util.cc(1360)] : X error received: serial 219251, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/142320.774244:WARNING:x11_util.cc(1360)] : X error received: serial 223637, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/142558.447072:WARNING:x11_util.cc(1360)] : X error received: serial 239171, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/142726.521980:WARNING:x11_util.cc(1360)] : X error received: serial 248331, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/142826.238107:WARNING:x11_util.cc(1360)] : X error received: serial 255585, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/142839.767432:WARNING:x11_util.cc(1360)] : X error received: serial 256980, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/142955.892723:WARNING:x11_util.cc(1360)] : X error received: serial 265173, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/142956.813046:WARNING:x11_util.cc(1360)] : X error received: serial 265290, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/142959.432132:WARNING:x11_util.cc(1360)] : X error received: serial 265578, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/143222.949019:WARNING:x11_util.cc(1360)] : X error received: serial 281060, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:465657856:0605/143534.668994:ERROR:interface_registry.cc(210)] : Failed to locate a binder for interface: chrome::mojom::ResourceUsageReporter requested by: exposed by: via InterfaceProviderSpec "service_manager:connector".
[1090:467363840:0605/143645.628365:WARNING:x11_util.cc(1360)] : X error received: serial 309303, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/143723.475624:WARNING:x11_util.cc(1360)] : X error received: serial 313203, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/143856.369847:WARNING:x11_util.cc(1360)] : X error received: serial 322809, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:467363840:0605/143856.369873:WARNING:x11_util.cc(1360)] : X error received: serial 322811, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
[1090:465657856:0605/144618.532846:ERROR:interface_registry.cc(210)] : Failed to locate a binder for interface: chrome::mojom::ResourceUsageReporter requested by: exposed by: via InterfaceProviderSpec "service_manager:connector".
I need to try to reproduce it with less tabs, but just had it while opening reddit.com in a new tab, this is what chrome_debug.log recorded when I grep on the PID:

[16268:466974976:0605/153533.445091:VERBOSE1:web_request_time_tracker.cc(181)] WR percent 4862: http://www.reddit.com/: 1/654 = 0.00302432
[16268:466974976:0605/153533.453999:VERBOSE1:web_request_time_tracker.cc(181)] WR percent 4873: https://www.redditstatic.com/listing-comments.AZZO7Kj_O88.css: 4/10 = 0.42846
[16268:466974976:0605/153533.459246:VERBOSE1:web_request_time_tracker.cc(181)] WR percent 4875: https://www.redditstatic.com/recommended-link.lfHS1Jq3eYw.js: 4/15 = 0.294237
[16268:466974976:0605/153533.460378:VERBOSE1:web_request_time_tracker.cc(181)] WR percent 4871: https://www.redditstatic.com/reddit.tZUIt2I7tuE.css: 1/16 = 0.0639477
[16268:466974976:0605/153533.461235:VERBOSE1:web_request_time_tracker.cc(181)] WR percent 4874: https://www.redditstatic.com/reddit-init.en.jMuJSWtBSUw.js: 4/17 = 0.257825
[16268:619769600:0605/153533.651467:VERBOSE1:syncer.cc(67)] Committing from types Bookmarks, Preferences, Passwords, Autofill Profiles, Autofill, Autofill Wallet, Autofill Wallet Metadata, Themes, Typed URLs, Extensions, Search Engines, Sessions, Apps, App settings, Extension settings, History Delete Directives, Dictionary, Favicon Images, Favicon Tracking, Device Info, Priority Preferences, Managed Users, Managed User Shared Settings, Encryption Keys, Experiments
[16268:466974976:0605/153533.717768:VERBOSE1:http_bridge.cc(351)] HttpBridge received response code: 200
[16268:466974976:0605/153534.250726:VERBOSE1:web_request_time_tracker.cc(181)] WR percent 4880: https://www.google.nl/_/chrome/newtab-serviceworker.js: 0/41 = 0.00637721
[16268:466974976:0605/153534.250817:VERBOSE1:web_request_time_tracker.cc(181)] WR percent 4879: https://www.google.nl/_/chrome/newtab-serviceworker.js: 0/42 = 0.009695
[16268:465657856:0605/153609.074480:WARNING:sad_tab.cc(206)] Tab Killed: https://www.reddit.com/

Find attached a chrome_debug.log from an invocation of chrome --enable-logging --v=1 --user-data-dir=. inside an empty directory.

Did a bunch of loads of sites in 2-3 tabs. Finally on the reload of reddit.com in the first tab it suffered from the endlessly spinning spinner again. Got the ow, snap dialog box twice, waited one time and killed it the second time.
chrome_debug.log.gz
215 KB Download
Process state at time of spinning of comment above:

18550  2  S+      0:34,49 chrome: TaskSchedulerForegroundWorker3 (chrome)
18558  2  S+      0:40,23 chrome: GL_ARB_timer_query (chrome)
18592  2  SN+     0:40,17 chrome: WorkerPool/499255808 (chrome)
18637  2  IN+     0:04,37 chrome: WorkerPool/674193408 (chrome)

S - sleeping for less than 20 seconds
N - process has reduced CPU scheduling priority (setpriority(2))
I - idle process (sleeping longer than 20 seconds)
+ - the process is in the foreground process group of its control terminal

Going to add --disable-gpu in the mix as well now.
Got another case (I am positive there will be a bunch of different ones causing the various problems).
This was started with chrome --disable-gpu --enable-logging --v=1 --user-data-dir=.

When it spun endlessly, the last drawn URL bar at the bottom showed "tracker.bannerflow.com".

Resolving that is not an issue:
% drill tracker.bannerflow.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 41195
;; flags: qr rd ra ; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; tracker.bannerflow.com.	IN	A

;; ANSWER SECTION:
tracker.bannerflow.com.	760	IN	CNAME	tracker-bannerflow.trafficmanager.net.
tracker-bannerflow.trafficmanager.net.	160	IN	CNAME	bf-tracker-us-west.azurewebsites.net.
bf-tracker-us-west.azurewebsites.net.	1660	IN	CNAME	waws-prod-bay-059.vip.azurewebsites.windows.net.
waws-prod-bay-059.vip.azurewebsites.windows.net.	160	IN	CNAME	waws-prod-bay-059.cloudapp.net.
waws-prod-bay-059.cloudapp.net.	60	IN	A	23.99.91.55

Although after just trying it again it took a few seconds before returning information. This is via a caching unbound setup.
chrome_session2_debug.log.gz
129 KB Download
Cc: kavvaru@chromium.org
Labels: Needs-Feedback
ashemedai@Could you please provide us any sample URL to reproduce the crash from our end.
Also please try the issue on latest stable 59.0.3071.86 and if the issue still persists please provide us the crash id from chrome://crashes.

Thanks,
Hi @kavvaru, I just reloaded reddit.com a bunch of times.

The 59.x release still needs to be committed to the FreeBSD ports, it's currently in lockdown in preparation for the release of FreeBSD 11.1.

As per https://www.chromium.org/developers/crash-reports Chromium crash reporting is disabled by default and I not yet sure if breakpad is compiled in or not. At least running with CHROME_HEADLESS=1 to see if it might give a minidump.

I don't frequently get ow, snap. Most of the time I just have spinners (both counter and clockwise).

I used www.nu.nl, www.reddit.com, news.google.nl - most of the time it seems to act up when trying to load ads, got a "Waiting for track.adform.net..." here in one tab and a "Waiting for pix04.revsci.net..." in another tab while visiting www.nu.nl.

What's in the viewport of the tab will display, but cannot scroll the tab.

Just got another one www.nature.com "Waiting for googleads.g.doubleclick.net..." None of them triggering any ow, snaps.

Got a 5 MB unpacked chrome_debug.log file if that is any help.

What other steps can I take to get information about what's happening?
Project Member

Comment 8 by sheriffbot@chromium.org, Jun 8 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kavvaru@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
Cc: rbasuvula@chromium.org
Labels: Needs-Feedback
Thanks for the update! Tested in chrome # 58.0.3029.110 and Stable #59.0.3071.115 and Canary #61.0.3160.0 on Ubuntu 14.04 and not able to reproduce the issue.unable to attach the screen cast due to huge MB.

@ ashemedai: Could you please let me know if i have missed anything and if possible,Please create new profile without extensions and apps.Re-check once in latest builds of the chrome and let us know the observations and please provide the crash id from chrome://crashes of the issue which would help us to triage the issue further.

Thanks in Advance.
@rbasuvula: yes, as stated a few times it concerns FreeBSD, not Linux. There's no OS option to pick FreeBSD in this issue tracker though, but it's stated explicitly in my first few posts.

As also stated: there's no crash id because chromium turns this off by default.

And also, as stated, I ran the last few sessions with a --user-data-dir=. inside an empty directory, which creates a new profile free from any extensions or apps.

So while I appreciate your update and questions/statements you effectively wasted your time and it adds nothing of value to this ticket. :\
Project Member

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

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "rbasuvula@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
Labels: TE-NeedsTriageFromMTV
Adding the label 'TE-NeedsTriageFromMTV' as the issue is related to FreeBSD.
Same OS version. Update all the ports. This includes an update of Chromium from the reported version to Version 61.0.3163.100 (Developer Build) (64-bit).

This seems to have resolved the spinning tab problem.

Please close this issue.
Status: WontFix (was: Unconfirmed)
Closing as per #13

Sign in to add a comment