From nobody@FreeBSD.org  Sat Feb  1 18:17:12 2014
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hub.freebsd.org (Postfix) with ESMTPS id A4546632
	for <freebsd-gnats-submit@FreeBSD.org>; Sat,  1 Feb 2014 18:17:12 +0000 (UTC)
Received: from oldred.freebsd.org (oldred.freebsd.org [IPv6:2001:1900:2254:206a::50:4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.freebsd.org (Postfix) with ESMTPS id 9176D123D
	for <freebsd-gnats-submit@FreeBSD.org>; Sat,  1 Feb 2014 18:17:12 +0000 (UTC)
Received: from oldred.freebsd.org ([127.0.1.6])
	by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id s11IHCVQ074428
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 1 Feb 2014 18:17:12 GMT
	(envelope-from nobody@oldred.freebsd.org)
Received: (from nobody@localhost)
	by oldred.freebsd.org (8.14.5/8.14.5/Submit) id s11IHCBh074418;
	Sat, 1 Feb 2014 18:17:12 GMT
	(envelope-from nobody)
Message-Id: <201402011817.s11IHCBh074418@oldred.freebsd.org>
Date: Sat, 1 Feb 2014 18:17:12 GMT
From: "John J. Rushford" <jjr@alisa.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Chromium 32.0.1700.102 hangs and becomes unresponsive.
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         186352
>Category:       ports
>Synopsis:       www/chromium 32.0.1700.102 hangs and becomes unresponsive.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    chromium
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Feb 01 18:20:00 UTC 2014
>Closed-Date:    
>Last-Modified:  Thu May 15 19:30:00 UTC 2014
>Originator:     John J. Rushford
>Release:        FreeBSD 10-RELEASE
>Organization:
none
>Environment:
FreeBSD susieq 10.0-RELEASE-p4 FreeBSD 10.0-RELEASE-p4 #0: Tue Jan 14 20:48:07 UTC 2014     root@amd64-builder.pcbsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
Usually when I start chromium it hangs with a white screen and the spinner twirling while attempting to load the startup page, www.freebsd.org.  After several minutes, there is a popup stating that the page is unresponsive and I then kill it.  If I hit the reload button, the scenario is repeated.

At other times after using chromium for sometime, the same behavior is exhibited when I try to navigate to a new website.

On the same machine, I can run Firefox without any issue.
>How-To-Repeat:
Set your default page and then stop/restart chromium.  In my case, the startup page is www.freebsd.org.  I'm also using the xfce4 window manager.
>Fix:
Switched to Firefox

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-amd64->chromium 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Sun Feb 2 14:29:14 UTC 2014 
Responsible-Changed-Why:  
make this a ports PR and assign. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=186352 

From: =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org>
To: bug-followup@FreeBSD.org, jjr@alisa.org
Cc:  
Subject: Re: ports/186352: www/chromium 32.0.1700.102 hangs and becomes unresponsive.
Date: Tue, 25 Feb 2014 20:04:26 +0100

 I just retried the first scenario (setting www.freebsd.org as start
 page, close and restart chromium) without troubles. Can you retry with
 version 33.0.1750.117 (svn commit r346060) ?

From: John Suykerbuyk <John@Suykerbuyk.org>
To: bug-followup@FreeBSD.org, jjr@alisa.org
Cc:  
Subject: Re: ports/186352: www/chromium 32.0.1700.102 hangs and becomes unresponsive.
Date: Thu, 15 May 2014 13:22:15 -0600

 I was seeing the same issue on Chromium 32, built and installed from 
 ports  34.0.1847.132 (265804) and still have the same problem.
 
 Running PCBSD with the following uname info:
 FreeBSD t500 10-STABLE-p7 FreeBSD 10-STABLE-p7 #3 2bfa6cd(stable/10): 
 Fri Jan  3 15:35:35 EST 2014
 
 Many of the problems "feel" like the issues related to 
 "kern.ipc.shm_allow_removed=1" when Chrome 24 came out in 2013.  I have 
 confirmed that I am running with all the recommended shared memory 
 settings (see list below).
 
 In particular, reopening Chrome with several tabs (>7 or 8) usually 
 results in at least one page dieing for having run out of memory.  
 Hitting reload brings the page back.  Also on sites like facebook and 
 Google+, Google Calendar, text entry becomes INCREDIBLY slow and 
 delayed, often times with the "unresponsive page" dialog popping up to 
 kill it.  Closing and reopening the page "fixes" it for a very brief while.
 
 I see nothing in var/log or dmesg that indicates a problem, nor have I 
 (probably due to ignorance) seen anything in Chrome's task manager or 
 JavaScript console that could be used to identify the problem.
 
 
 I've had no similar issues with Firefox.
 - John "S"
 
 sysctl -a | grep kern.ipc
 
 kern.ipc.maxsockbuf: 2097152
 kern.ipc.sockbuf_waste_factor: 8
 kern.ipc.max_linkhdr: 40
 kern.ipc.max_protohdr: 60
 kern.ipc.max_hdr: 100
 kern.ipc.max_datalen: 68
 kern.ipc.maxmbufmem: 3056840704
 kern.ipc.nmbclusters: 373150
 kern.ipc.nmbjumbop: 186574
 kern.ipc.nmbjumbo9: 165843
 kern.ipc.nmbjumbo16: 124380
 kern.ipc.nmbufs: 2388165
 kern.ipc.maxpipekva: 98492416
 kern.ipc.pipekva: 2134016
 kern.ipc.pipefragretry: 0
 kern.ipc.pipeallocfail: 0
 kern.ipc.piperesizefail: 0
 kern.ipc.piperesizeallowed: 1
 kern.ipc.msgmax: 16384
 kern.ipc.msgmni: 40
 kern.ipc.msgmnb: 2048
 kern.ipc.msgtql: 40
 kern.ipc.msgssz: 8
 kern.ipc.msgseg: 2048
 kern.ipc.semmni: 50
 kern.ipc.semmns: 340
 kern.ipc.semmnu: 150
 kern.ipc.semmsl: 340
 kern.ipc.semopm: 100
 kern.ipc.semume: 50
 kern.ipc.semusz: 632
 kern.ipc.semvmx: 32767
 kern.ipc.semaem: 16384
 kern.ipc.shmmax: 536870912
 kern.ipc.shmmin: 1
 kern.ipc.shmmni: 1024
 kern.ipc.shmseg: 1024
 kern.ipc.shmall: 131072
 kern.ipc.shm_use_phys: 0
 kern.ipc.shm_allow_removed: 1
 kern.ipc.soacceptqueue: 128
 kern.ipc.numopensockets: 354
 kern.ipc.maxsockets: 192375
 kern.ipc.sendfile.readahead: 1
 
>Unformatted:
