From owner-freebsd-chromium@freebsd.org Mon Oct 30 15:06:29 2017 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1B74E5F511 for ; Mon, 30 Oct 2017 15:06:29 +0000 (UTC) (envelope-from bounce-freebsd-chromium+freebsd.org@streturns.eu) Received: from mx-out-gi2.emailamp.com (mx-out-gi2.emailamp.com [89.238.184.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 71685661AA for ; Mon, 30 Oct 2017 15:06:22 +0000 (UTC) (envelope-from bounce-freebsd-chromium+freebsd.org@streturns.eu) DKIM-Signature: v=1; a=rsa-sha256; c=simple; s=email; d=emailamp.com; h=Reply-To:Content-Type:MIME-Version:Subject:List-Unsubscribe:From:To:Date: Message-ID:From:To:Subject; t=1509375985; x=1509397585; bh=g6SfNTd6I8m8/+K3VZlVyESH6Nzx1eB4heEm1JS0rPI=; b=WUpUGPBh6h9zgbOLrhUAETi6T4QqiB54A71AZ7kmIcMbXu6SHmr2gGfH7XwxeT/vRdeSiMUjWRJ7 VQPTyYDkvofpP9LerEAebXClmoDY+CeRPBNtZ8l0NyOJn8jrH/FnF6Bl30CzBQ4bOtKqUmZr9uxG CRgLHzBjdnUGx89KQQvM5M8+4G6qmGCynu3UCTymK1+xFXGfiGloQQnRadlWHjYolXFYYq/O4DRd mT6nLI+rITuX2FKz3XRq1sTzoIpbqYUAQZODpmwcp03xZ19jQbgbbC2JIW4IvK3LdGEH7Son26f2 Y8udKyeJDk7kcxQbC3w+doby0jfLpsmCF+XeRw== Received: by mx-out-gi1.emailamp.com id husvv22akmcn for ; Mon, 30 Oct 2017 17:04:56 +0200 (envelope-from ) Reply-To: MIME-Version: 1.0 Subject: 20 Beautiful Bedroom Curtains From: Housublime To: freebsd-chromium@freebsd.org Date: Mon, 30 Oct 2017 15:04:58 -0000 Message-ID: <59f73e5004f89f40e6717c69@housublime.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2017 15:06:30 -0000 | ![](http://nl.housublime.com/7RcjIqkyPGwc60pA7UplNRcEyigxRS2Rz43zPLAgZGBM= 4Nu1iKcejd-Dccsoj1s-D6sE2vEOmtDM5Lru_bmtbmRlJKY-NLGPWUQhUXAKqNvBNpmTW0oiU4r= CGYX1sibVVAZdAFUrNhOZKWa4z0g-YJZcyBTsfoNhaJEOoL_4A-cBoUmKc5FbeTWXSBdWIhXhHt= -nW9slkjgM2Nf2UZxbkaNre2k2zTHCKc6DZuGIlxvoXySWA1X4EfFld-619PSR-9POc7n1okEvJ= vtBQoewo3tVn38_GMPH_qQki25gduffr_i3zkqdfImmmQ-pdhu1LqQe9jafXnoZ4Hk_WRlWdw_r= lKyUPILIToA1mFySD1F2zUQGFXx63-yO86JHkBfwAtMpwg_5K2x-Z1crmRVut0FYunR5TgfTQjW= r_KOvSY52KnpsHAoD3vgr1oHoR8xzpk-lJ0BUlTm0qIAUtfFeKMzz2PYCtz1HYSgTwF6V989i0X= -Q) =20 --- =20 | | [ ![](http://nl.housublime.com/2uvmLxb8my4jlFGR4LzAH-AbaUrXK36Q4pveNgt= KLId3kRCZoSMzCctYEh6RjiHfLwpi9z-ZuOhCny6jVqELInNVZb6d67gkJ3KGmsro-eKo1_K0Fu= JOws-ThupgdUheDsH73YcVA8tj1gBVcjX237OIo3hXd7patxK80JFBbb354_vLHDgTZEOH9CK0O= 9T9Eyxqf50MlwM3u4H2zASU53O6uKTaFmEv-IuxAAJCWEJjTOkgwdkkbxqPCvl10riMF_r-MNmM= N2olK2cFPVqOgBnTpkF9tnTIfINzYsyrKmRZfyBpp6P3ZwETddcFBg_Zo2MlYSwD_t-ilSFMCc0= 9AKCz5gu6QcuDs8lzh8tY0haqioZ3ZnpupZbNgugB-o_7LBbcNEkLK4QUBR-M79kDxEjiR8UgOX= lM9LFF5ceJLvjbIUXwhU5NQF5Jk-_k2FOFPKayCSYVy1o3AwWX5M1HIKris8CXKWSnuZCPXbTyn= nKe2EcduVjWQAzyIc8acWLWmywCVu1DErkuAIuJsYFjN4-KptrQan4vvUA0yw) ]() =20 --- =20 | ## [ 20 Beautiful Bedroom Curtains ]() If you're looking for some fabrics to refresh your bedroom, check out these= 25 inspiring curtain ideas that will help you obtain an easy makeover with= out too many stress. =20 =20 --- =20 | [Open gallery =E2=86=92]() =20 --- =20 | You received this email because you are registered on http://nl.housublime.= com/MW6bvPE7FBXkJnztl2bngAUpW7hiEGM34BSM6G5t-5sBYJLqlmBIFmOwN1v7WDbew6SfqDW= gqwPuSQMKqgmDkOUORzH4jsEJtybMMbANELxM_vQu1S5Pg-i5ENVdGjqMIL2vIBZpHUpflRbJYb= wkDB2KN4Ya2BA9XbylAALktZx_-mkRE_-RCc1Oz5LHtyb4nsmHgkxAkVLX8FdR0D4BV_0jk6bQ8= fGYEQp9ykub6TkyKz04urTJwilPI0b6b9zHKbjtDegs0NKK5wV1NFRA2nyXceo2CyAA9z8WbYd7= G_-5LZCYKZpc7YN7I4drN-cIiEFg_vZT2cMfHuiJzSzMcoZ7xLoqYEmZj5sAEAMOa2TYUn0MP4Z= KxKyTUdGMB8A1QQc2MNeeMj-ck8uNPONOAQed9jkBAwD6gFplIBnT9xv58FGDgUlMjCQ8fhkbc-= LXQKfmgthvTIxbHq9x7g. We respect your privacy. If you believe this has been= sent to you in error, please safely unsubscribe. =20 =20 --- From owner-freebsd-chromium@freebsd.org Thu Nov 2 15:13:38 2017 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0CE2E5C3F8 for ; Thu, 2 Nov 2017 15:13:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B7A9D821B7 for ; Thu, 2 Nov 2017 15:13:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B7109E5C3F7; Thu, 2 Nov 2017 15:13:38 +0000 (UTC) Delivered-To: chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6B96E5C3F6 for ; Thu, 2 Nov 2017 15:13:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9D319821B6 for ; Thu, 2 Nov 2017 15:13:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vA2FDXeu094315 for ; Thu, 2 Nov 2017 15:13:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 212812] www/chromium: tabs "hang" 10% of the time Date: Thu, 02 Nov 2017 15:13:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: vince.mulhollon@springcitysolutions.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2017 15:13:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212812 --- Comment #33 from Vince Mulhollon --- Problem seems to be getting worse over the last few months and last few upgrades, to the point I've had to switch to Firefox recently now that tab rendering success rate is well below 10%. With no change in rate of tab rendering failure I have tried the following = from the bug report: Disable V8 caching in chrome://flags (which also takes 10-20 attempts to render) Wipe .config/chromium (multiple times... first time I did that I wiped over= a gig of junk) Disable hardware acceleration in chrome://settings "Use hardware Accleration when available" Multiple machines: I have three desktops using NFS home / LDAP etc so its trivial to try chromium across multiple machines, all with identical proble= ms. I had various older proprietary nvidia driver software on my multiple machi= nes, I've upgraded the machines multiple times since the problem began per nvidia-smi as of today I'm running the latest "Driver Version: 384.59" and there is no change in tab hanging. Because I have multiple different machines on the desk I've experienced the same failure on six nvidia cards of various ages and models: two older (cir= ca 2014) geforce gtx 730 connected via analog vga 1280x1024, one ancient (circa 2011) geforce gtx 560ti DVI connection 1600x1200, and three new (circa 2017) geforce gtx 1050ti displayport connection 2560x1440 144 hz. I have no hard= ware problems running CPU/GPU intensive workloads for hours without any crashes = such as firefox or minecraft. The bug I'm experiencing is solely related to chromium tab opening failing 90%+ of the time; never a graphics (or other subsystem) hang or kernel crash. I can and do run onshape.com for hours in firefox, which is an online html5 professional CAD program which would seem= to torture test 3d graphics rendering and hardware acceleration in a html5 browser. I have an onshape CAD drawing open in another tab in firefox while I'm typing this; flawless operation, at least in firefox. Whatever is wron= g, it probably doesn't relate to graphics hardware or hardware acceleration or graphics drivers given that chromium hangs the same way and same rate of failure regardless of whatever hardware I throw at it; admittedly I don't h= ave access to any non-nvidia graphics hardware. I've tried a couple combinations of the above ; old card with disabled hard= ware and disabled caching but latest driver, wipe the config and no caching but enable hardware, sorry but I didn't record all my mixtures of experiments. = No change in failure rate under any condition. One of the machines has front mounted drive trays; stick a drive tray boot drive with a SSD with devuan (basically, a debian distro) linux installed a= nd everything works with every nvidia hardware card. Ditto win10 and win7. I don't have drive trays on the other two freebsd machines. I find it fascinating that the failure rate is not 100% or 0% but is roughly 90% and for a given version of chromium regardless of hardware, the rate of failure in the long run is constant regardless of what I try, a sparse and graphically bare intranet of a couple K of pure html and CSS and no JS fails equally often as some social networking site with 5 megs of spyware and ad links and JS. I opened and closed a gmail tab on another machine on my des= k in chromium 13 times before it worked, whereas the intranet took 8 tries, but = I've seen those numbers reverse before. The standard deviation is very high, sometimes (although VERY rarely) tabs render in as little as three attempts= .=20 Its been a long time since a chromium tab renders on the first try; maybe a year now. All three machines are running SSDs. Two have 1/4 tb raid1 mirror arrays w= ith zfs; the third drive tray machine has a 120 GB SSD for freebsd. Two machin= es have 16 GB of RAM one has 8 GB. I'm playing with one machine as I'm typing this, trying to open a gmail window and top reports 2925M free with 0 swap = use; whatever's wrong its not because its starved for memory or cpu load is too high. All three motherboards are older AMD64. I work in a secured "armed guard" type of environment, so once I got a tab = to gmail to work, I was able to leave the tab open and running on a physically secured machine; once a tab initially renders, if it doesn't hang when open= ed of course, performance is excellent and there are no weird crashes even aft= er days of continuous use of the same tab. No slowdowns, no bugs, no weird rendering, no kernel crashes, no weird syslog lines, no memory leaks (none = that hit within a week or two anyway) Either it fails to begin to render or it works and that one tab will continue to work for at least a week of continu= ous use. I have access to an extremely large vmware cluster so this morning I spun u= p a freebsd host on the dev vlan and installed chromium 61.0,3163.100_1 ... I c= an connect to the vmware image using rdesktop and its slow but tabs work 100% = of the time. That is interesting because its the same OS with the same ansible-enforced packages configuration and installation but if it runs on = bare hardware the chromium render hangs, but if I run it on virtualized hardware= it works perfectly (well, slowly as you'd expect...) Neither ansible nor the = OS "know or care" that one machine is bare metal hardware and the other machin= e is a virtual image, from an ansible configuration standpoint the only differen= ce between the three bare metal installs on my desk and the virtual image on t= he cluster is ip addrs and hostname. Obviously the hardware is different; the cluster is intel hardware and the cluster image devices are virtual not bare metal and silicon. dmesg on the identical ansible-configured virtualized image reports "vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0".=20 /var/log/Xorg.0.log reports its using the vmware x11 driver "[ 11.742] (= --) vmware(0): VMware SVGA regs at (0x1070, 0x1071)" I believe there is a way = to pass thru GPU access to a vmware image and I'm obviously not doing that. The fact that chromium renders tabs fine when an identical image is virtual= ized and run without the nvidia driver, connected via a rdesktop session, would = seem to point to the nvidia driver GPU acceleration as the problem, although the nvidia driver operates perfectly with all other software on the machine including extremely graphically intensive software and the only symptom of = any sort ever is creating tabs fails to render almost all the time only on chro= mium seems to point to a problem with how chromium talks to nvidia driver WRT so= me kind of hardware acceleration that cannot be disabled from options in the browser config. Its also odd that the driver fails only 90% of the time and the failure rate appears unrelated to system workload or complexity/size of= the page to be rendered or physical nvidia card hardware model. I wonder if I opened 100000 tabs, using some kind of GUI automation software that might not even exist, if the failure rate converged to 15/16th of the time. If when opening a tab, some random stack address or something has to randomly line up precisely on a perfect 16 byte address boundary or it lock= s up the thread. I wouldn't even know where to begin to look, but I do have a g= ut level feeling the failure rate, if it could be measured, is currently exact= ly 15/16th of the time, and somewhere a 128 bit long "something" is only being stored correctly 1/16th of the time. If anyone has any ideas or suggestions for experiments, please advise. I'm outta ideas, and firefox works great, and the only reason I care anymore is= my chromebook uses chrome so it would be nice to sync my desktop and my chrome= book bookmarks, whatevs... Have a pleasant day and thanks for your efforts thus far and in the future = and good luck with this tricky bug! --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-chromium@freebsd.org Thu Nov 2 17:15:41 2017 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E04CE5EDCF for ; Thu, 2 Nov 2017 17:15:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E9A0919DD for ; Thu, 2 Nov 2017 17:15:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E5F70E5EDCE; Thu, 2 Nov 2017 17:15:40 +0000 (UTC) Delivered-To: chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3C7AE5EDCD for ; Thu, 2 Nov 2017 17:15:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB9A219DC for ; Thu, 2 Nov 2017 17:15:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vA2HFaew086738 for ; Thu, 2 Nov 2017 17:15:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 212812] www/chromium: tabs "hang" 10% of the time Date: Thu, 02 Nov 2017 17:15:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: robbelics@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2017 17:15:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212812 Rob Belics changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robbelics@gmail.com --- Comment #34 from Rob Belics --- (In reply to Vince Mulhollon from comment #33) I've had to do the same but, being a web dev, I must use chromium for testi= ng. What I've found is, if I leave chromium running in one window (I have the bookmarks manager in that) and open a second window, I can often surf for q= uite a while, even with multiple tabs, before having problems. --=20 You are receiving this mail because: You are the assignee for the bug.=