From owner-freebsd-chromium@FreeBSD.ORG  Wed May 25 20:11:00 2011
Return-Path: <owner-freebsd-chromium@FreeBSD.ORG>
Delivered-To: chromium@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 780691065677
	for <chromium@FreeBSD.org>; Wed, 25 May 2011 20:11:00 +0000 (UTC)
	(envelope-from gtodd-1306353132.73393@iciti.ca)
Received: from mailout.easydns.com (mailout.easydns.com [64.68.200.141])
	by mx1.freebsd.org (Postfix) with ESMTP id 38BFF8FC28
	for <chromium@FreeBSD.org>; Wed, 25 May 2011 20:10:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by mailout.easydns.com (Postfix) with ESMTP id 387025811
	for <chromium@FreeBSD.org>; Wed, 25 May 2011 15:53:05 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at mailout.easydns.com
Received: from mailout.easydns.com ([127.0.0.1])
	by localhost (mailout.easydns.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4MMXWUYjdTff for <chromium@FreeBSD.org>;
	Wed, 25 May 2011 15:53:04 -0400 (EDT)
Received: from wawanesa.iciti.ca
	(CPE0080c8f208a5-CM001371173cf8.cpe.net.cable.rogers.com
	[99.246.61.82])
	by mailout.easydns.com (Postfix) with ESMTPA id 12E2456D3
	for <chromium@FreeBSD.org>; Wed, 25 May 2011 15:53:04 -0400 (EDT)
Received: (qmail 73394 invoked by uid 1001); 25 May 2011 15:52:02 -0400
Date: 25 May 2011 19:52:02 -0000
Message-ID: <20110525195202.73393.qmail@wawanesa.iciti.ca>
From: gtodd@iciti.ca
To: chromium@FreeBSD.org
X-Mailer: 822mess.c qmail-injected by hand babyee!
X-Mailer: Composition by my friend ed(1)
X-Mailer: Follow me using e-mail messages.
Cc: 
Subject: Any attempt to print with chromium causes sigsev
X-BeenThere: freebsd-chromium@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD-specific Chromium issues <freebsd-chromium.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chromium>, 
	<mailto:freebsd-chromium-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chromium>
List-Post: <mailto:freebsd-chromium@freebsd.org>
List-Help: <mailto:freebsd-chromium-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chromium>, 
	<mailto:freebsd-chromium-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2011 20:11:00 -0000

Hi, I think this is a well known bug? Should I file a PR on 
the port?  

The main chromium development platform seems to be Windows (and
some Linux) where the bug does not manifest. Upstream they'd like
bug reports with backtraces and patches! I am attempting to build
a debug version of trunk to see if this has been resolved and get
a meaningful trace on the crash with our latest version. 

These are non-trivial operations at this site ;-)

Since this seems difficult to patch/fix for FreeBSD should the crash
be mentioned in UPDATING or pkg-message?

Regards,

GRT