From owner-freebsd-chromium@FreeBSD.ORG Fri Jun 8 12:11:16 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D82931065670; Fri, 8 Jun 2012 12:11:16 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 7DD878FC17; Fri, 8 Jun 2012 12:11:16 +0000 (UTC) Received: by qabg1 with SMTP id g1so713004qab.13 for ; Fri, 08 Jun 2012 05:11:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Y9JHFN2J6G4VCpMW10O6XKWRFF7WJsS7XzgiRZCLUfw=; b=pmM6OmyVZYWuq0TXaUd/SD/S+4ui5binKHTyIk5f8nSMI5UyVqrgQcborHgi22ePV8 LVp6iq01FYc17bTSu/QSDeywUzg3KngN/2utfZVvuQm+araPOslYg8p8KleT8ZPPO9Aj 76kbCXoIbj3E/KohzuWqOqbPNmAmUTHly0iL/kOM5//lvtz01xRsSzjqF1u1c9p59Kd/ u2//nrxjCPPYsIsuomXvBPTfIAXjxGExL+RRKGsDRPowAS9wPRB9O7sbYufHkvRnxjik Hsiq6m2v7u+1JQa2JO5bK7cjFVsxyv12xzXlhsDIPHwRFPmjwWHyRSt+5WcN7effwYF8 kj7w== MIME-Version: 1.0 Received: by 10.229.135.5 with SMTP id l5mr1762316qct.41.1339157474972; Fri, 08 Jun 2012 05:11:14 -0700 (PDT) Received: by 10.229.155.2 with HTTP; Fri, 8 Jun 2012 05:11:14 -0700 (PDT) In-Reply-To: References: <20120607060457.GC98376@ithaqua.etoilebsd.net> Date: Fri, 8 Jun 2012 15:11:14 +0300 Message-ID: From: George Liaskos To: "David P. Caldwell" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-chromium@freebsd.org Subject: Re: Chromium 19 dumps core on 9.0-RELEASE (i386) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 12:11:17 -0000 On Fri, Jun 8, 2012 at 2:46 PM, David P. Caldwell wrote: > On Fri, Jun 8, 2012 at 3:46 AM, George Liaskos wrote: >> On Thu, Jun 7, 2012 at 9:04 AM, Baptiste Daroussin wrote: >>> On Wed, Jun 06, 2012 at 07:34:05PM -0400, David P. Caldwell wrote: >>>> I built the latest Chromium 19 by building against the 9.0-RELEASE >>>> *packages*. I did not want to update all my ports and incur the >>>> various library problems that resulted the last time I tried that. I >>>> may try it next. >>>> >>>> I am rebuilding with debug symbols, as when I tried to view >>>> chrome.core in gdb, it just gave me a huge backtrace of "??" >>>> instances. >>>> >>>> I had Chromium 18 running successfully with an older version of the >>>> ports tree, built from source. But I can't reproduce that. >>>> >>>> I'm building inside a VirtualBox instance, if that makes any difference. >>>> >>>> I recognize this all may not be a very useful bug report, but I'm >>>> still learning to file useful ones, so please bear with me. >>>> _______________________________________________ >>>> freebsd-chromium@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium >>>> To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org" >>> >>> Confirmed, I got the same on my eeepc. >>> >>> regards, >>> Bapt >> >> Debug build works for me under i386 vm, release crashes... I didn't >> have enough time to debug this. >> >> Feedback is always welcome and needed. >> >> >> Regards, >> George > > What do you mean by "debug build" -- one with debug symbols enabled > during make configure? > > I tried to build that and the build failed, and I gave up at that > point, but I can keep trying. > > Of course, the reason I was trying to do the debug build was to find > the problem, but are you saying that enabling the debug symbols > somehow fixes the problem? > > -- David. Yes, with the debug option enabled chromium does not crash. It only produces some error messages from the GPU thread about libGL being old. Most probably you are running out of memory, that is why you cannot finish the compile. I had to add swap.. even though my desktop has 16GiB of ram they are not usable from the vm, i will try to recompile the kernel with PAE.