From owner-freebsd-chromium@freebsd.org Sun Sep 4 08:21:04 2016 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 E326ABCFC87 for ; Sun, 4 Sep 2016 08:21:04 +0000 (UTC) (envelope-from aminchik81@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C039DB43 for ; Sun, 4 Sep 2016 08:21:04 +0000 (UTC) (envelope-from aminchik81@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id e124so105445144ith.0 for ; Sun, 04 Sep 2016 01:21:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=3xhMCFNf84cHh8RL9NlJPKbiHKlGE4pmq37jergCFWc=; b=k4t0SeZ8ngggp0Pv8FKxPLHLqBNVXr3wVjyytVpYCUloSUcJzRsQOmbgDHYycB1I1D PpxcUbRJmerLclig5sHXmVfLJkgbkRt62V87n5iNo2Gun6Ro/hd0e3jIu7KTj3e2zLp2 RpPjR+hWJBAfPh8HXA2aH2IaH1vvu2LnfC7bGxLKtUMZMB0hqmUbqgSMQltxPqobTXWI x3wYletsjb2F90xEAWZ6Q/CJwCsIxi8G8tuJgwD7ggZp+7oK4pd+T+VK9MLSneNGe1xP Vj4U5NDWc19g5TwhwlnpRxxc+3NQIIP9JYocTrNYcCRiBcfij/D4sgXy7BHDxDwQhumb 3wrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3xhMCFNf84cHh8RL9NlJPKbiHKlGE4pmq37jergCFWc=; b=hUEcTFIw/Yo54rGcmXmurSjY5bzMlyryH9S9JNDoWHRvSnQla9mmQhOmrsE1HJO81X 4u4Z2bSaLDSaPrRJyDgU8PplA7XZ2UZDrhpphkjxYp3nFcPZCfmPZYhzDzLF+7ckmphY caaUIJLlyIqSQE+9SJCf88SjxqKeiMVhlcrqH9bIiTg1DqmPv+xxKzBmaqO2S2TKV6DE sSx4FBpa7aX50t7nyOuDUqqOjfehBYcGOGOtJKN95E2G+UOqAob98i47aMNkZgwpU8ky 7aBURL9xfK/xQcs7sPVxYFHOPR93E2OtYShPagBIKgIx0qSxF4BA2DMFs3OHRSuVOU2Q q2Ng== X-Gm-Message-State: AE9vXwP9yPZgmLBNlseufgxQn+2zEUOfD82ejPpS28uVhsCB/2CfvLw+vucq887DbUJilf60nwVAcNEDG+XFZw== X-Received: by 10.36.237.206 with SMTP id r197mr14722367ith.56.1472977264014; Sun, 04 Sep 2016 01:21:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.41.194 with HTTP; Sun, 4 Sep 2016 01:21:03 -0700 (PDT) Received: by 10.79.41.194 with HTTP; Sun, 4 Sep 2016 01:21:03 -0700 (PDT) From: =?UTF-8?B?0JDQvNC40L0g0JzQsNCz0L7QvNC10LTQvtCy?= Date: Sun, 4 Sep 2016 01:21:03 -0700 Message-ID: Subject: yhyqsq+ hth To: freebsd-chromium@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Sep 2016 08:21:05 -0000 raasqsqqsrw q aasqwesqa aatxxyaqaasa From owner-freebsd-chromium@freebsd.org Sun Sep 4 10:42:54 2016 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 82900A93E8E for ; Sun, 4 Sep 2016 10:42:54 +0000 (UTC) (envelope-from clutton@zoho.com) Received: from sender153-mail.zoho.com (sender153-mail.zoho.com [74.201.84.153]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6FDF3B3A for ; Sun, 4 Sep 2016 10:42:54 +0000 (UTC) (envelope-from clutton@zoho.com) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=message-id:subject:from:to:cc:date:in-reply-to:references:content-type:mime-version; b=Yeord1DoYURNYCOj6Pl5SZGNG3l80CTuWVxCLgzO1mmz6h1MoN5DelRwjkdeI5TMrWE8hW6Z9DD+ Ezb9wU3ngX0Gv9+3y9Awb9XciOvBro6rF8h46Jzuyak6wz6n7RzH Received: from [192.168.11.5] (mktechs.net [46.229.54.117]) by mx.zohomail.com with SMTPS id 1472985755909658.76842004062; Sun, 4 Sep 2016 03:42:35 -0700 (PDT) Message-ID: <1472985750.17294.22.camel@zoho.com> Subject: Re: 52.0.2743.82 (64-bit) to go, Aw snap is still there From: clutton To: Arto Pekkanen Cc: freebsd-chromium Date: Sun, 04 Sep 2016 13:42:30 +0300 In-Reply-To: <1d42dcb1faf8cbe4fbf24066a4163134@kapsi.fi> References: <1471486169.7533.8.camel@zoho.com> <1472667320.8146.46.camel@zoho.com> <1d42dcb1faf8cbe4fbf24066a4163134@kapsi.fi> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-LTnLIU3AG712P9+Uj4hC" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 X-Zoho-Virus-Status: 1 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: Sun, 04 Sep 2016 10:42:54 -0000 --=-LTnLIU3AG712P9+Uj4hC Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, 2016-09-04 at 02:30 +0300, Arto Pekkanen wrote: > So I was right from the very start: the Chromium codebase assumes=C2=A0 > certain behaviour from the memory allocation API of the host system, > and=C2=A0 > if this behavour is not in line with Linux (and Android), then > problems=C2=A0 > are to be expected. Yeah. Yet another fine example of how Open Source > is=C2=A0 > becoming synonymous with "Designed for Linux". >=20 > Is there any hope to get these changes propagated upstream to > Chromium=C2=A0 > developers? >=20 > It would be really nice to have upstream collaboration, because if > the=C2=A0 > upstream yet again changes things ever so slightly, things will=C2=A0 > mysteriously break. No, you wasn't right about the memory. I just wrote - base allocator works fine. Their home-brew assembler snippets work fine. I haven't checked blink allocator as thoroughly as base, may be it's there something not right. Do not assume that chromium is bug-free also. Some shit may fire with conditions met. For now I have GN ninja fully working (I believe I'll commit today), I doubt that google would take it upstream, such a mess to add another architecture. Nevertheless - I'm using macros=C2=A0is_bsd, with assumption that code would use OS_BSD, and with some division OS_OPENBSD/OS_FREEBSD further in C/C++ code, so it's more clean and has more chances to be accepted. But may no mistake - they invest a lot of resources to make this chrome work according to a plan, I don't think that they would add another OS. Unless there are a lot of people interested. About Linuxism, - they divide code very simple, if you don't like the functionality, you can rewrite it for your OS... The thing is - we use a lot of code written for Linux. > clutton kirjoitti 31.08.2016 21:15: > >=20 > > On Thu, 2016-08-18 at 05:09 +0300, clutton wrote: > > >=20 > > > I've just fixed the Aw, snap. I believe so. > > Ok, time to admit the defeat. I haven't fixed the issue in time, > > and I > > planned to do so till the summer is there. Being to much arrogant I > > started just before the end of time. I still can't believe I > > haven't > > fixed this in time. > >=20 > > I'll work on this, but not so intensively, now I just can't left > > it. > > I learned about the codebase so much. And all those small > > improvements > > shouldn't be wasted anyway (I haven't posted any because they worth > > nothing without fixing the bug). I'll do it more slowly and > > considerably now. > >=20 > > Number 1 issue is to bring new gn ninja generation system, every > > documentation assumes that you use gn, in future they will remove > > gyp > > generator. It would be much easier to work then. > > Number 2 is probably to clean the mess in our pathes. > >=20 > > Some thoughts for maintainers/developers: > >=20 > > Don't try debugging if you don't have enough RAM, I distributed the > > compilation to distcc, but RAM was an issue, even with another ssd > > attached as a swap it was tooooo slow to work with debugger, I did > > a > > lot of tricks to make it possible though, And have a lot of > > frustrations when those tricks mangle the code. I wish I could just > > put > > that monster in RAM press bt and don't wait 5 minutes till it's > > done. > >=20 > > Memory allocation in base works fine, I might missed something but > > debugging bit after bit was fine, then I finally did stubs, then I > > finally found that new shim allocator have those stubs already, > > some > > fixes would be needed though, for now I used this: > > allocator_shim_default_dispatch_to_libc.cc > > extern "C" { > > void* __malloc(size_t size); > > void* __calloc(size_t n, size_t size); > > void* __realloc(void* address, size_t size); > > void* __memalign(size_t alignment, size_t size) { > > =C2=A0 void *ret; > > =C2=A0 if (__posix_memalign(&ret, alignment, size) !=3D 0) { > > =C2=A0=C2=A0=C2=A0=C2=A0return nullptr; > > =C2=A0 } else { > > =C2=A0=C2=A0=C2=A0=C2=A0return ret; > > =C2=A0 } > > } > > int=C2=A0=C2=A0__posix_memalign(void **ptr, size_t alignment, size_t si= ze); > > void __free(void* ptr); > > }=C2=A0=C2=A0// extern "C" > >=20 > > But they assume linux and android, and they implement > > posix_memalign > > through memalign, I did the opposite. For now I have that > > unnecessary > > chain. It works but it could work faster without chain. > >=20 > > I haven't debugged heavily blink memory allocator, which I should > > have > > done instead of base allocator... There are some approaches to make > > it > > not to crush, but they are just hardcode patching, not fixing. And > > some > > patches I thought work just delaying the freezing. > >=20 > > Next, chromium team patch libraries, those in third_party > > directory, I > > debugged some of them, seems fine. No difference in work comparing > > to > > our. But that is probably is something to look at more. Ninja > > sucks, > > once I put the most recent re2 library by mistake and ninja > > compiled it > > without hesitation. Then I had coredumps on that library. > >=20 > >=20 > > Ok, probably all, because writing everything would be to much for > > non > > prepared reader. Better send patches. "Talk is cheap. Show me the > > code" --=-LTnLIU3AG712P9+Uj4hC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJXy/qWAAoJEH2wP42yyP6QunIQAIW9W6L8TrSLdtf74bFOaDzO ixMsmtAzvJZWFkhhMXDB6+1CC5unxqMDI9kcFNm7oOxSTtvnbDkGmGBQ6fOkCpLI aqsOLJ7PmgeAaiYc3cnJ1OM5RC8q6r/gmiZkIh5rJvQCmebI6bSbqFVtVXm1EpR/ 3gbuwOArJR2wNcLqle28PI3vUjp+s0cU1HPb8J1uIIPf/g3oETau5utk4FU3cDlo 6TeQSlK2ztzEctDkgSAJip65YfqqYNMwMwklP9gVV9E/S0uC0ozPfcSE19y3IcXc kdRoi5P0DMeDiPZrSa0AD3HQeTpqFeR0LCxlbBWTkOOlZo80fK3/nvyScbuwZwZU /d4qDYVRQpCmbr/CMKhD5LWD9MI9dQDkYSKkpRRcjq5g35utJae8y85dlTGqrkYL hiOo64CotCr2g4jxwgRnfW1eAOFeZlpwESXikOC09eZPRpUnr7APWflAS36ifI0e 0r2hRhQ/qqo3VU8Uxyw67Kmg/bbbvv5GnK5zYWGs75CdvGPSC5Y8iVoxfD7fwq2M tiAMuScpD3ffVvGcemzAkV7pwfX9lmw+/K9Dia8TjD0yX8QoxV9sAfgWycSVA4Uu RJx6WQVro+jEsgUT4vnJtELb0PW0Z6dVfREuwGn6D/ectlAS/h1ngw2DxTJ4r0Sk TAs+hS9I1nZUgLilYM1X =WoMj -----END PGP SIGNATURE----- --=-LTnLIU3AG712P9+Uj4hC-- From owner-freebsd-chromium@freebsd.org Sun Sep 4 21:00:49 2016 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 1BB40B718B0 for ; Sun, 4 Sep 2016 21:00:49 +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 08A0ABCF for ; Sun, 4 Sep 2016 21:00:49 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 07FCBB718A5; Sun, 4 Sep 2016 21:00:49 +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 07AB6B718A4 for ; Sun, 4 Sep 2016 21:00:49 +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 D9C73BCB for ; Sun, 4 Sep 2016 21:00:48 +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 u84L01uN021693 for ; Sun, 4 Sep 2016 21:00:48 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201609042100.u84L01uN021693@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: chromium@FreeBSD.org Subject: Problem reports for chromium@FreeBSD.org that need special attention Date: Sun, 04 Sep 2016 21:00:48 +0000 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: Sun, 04 Sep 2016 21:00:49 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 201805 | [PATCH] www/chromium: enable native message servi Open | 201805 | [PATCH] www/chromium: enable native message servi 2 problems total for which you should take action. From owner-freebsd-chromium@freebsd.org Thu Sep 8 18:32:00 2016 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 96669BD2878 for ; Thu, 8 Sep 2016 18:32:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8054C86B for ; Thu, 8 Sep 2016 18:32:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7FAC9BD2877; Thu, 8 Sep 2016 18:32:00 +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 7F536BD2876 for ; Thu, 8 Sep 2016 18:32:00 +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 6F4CE86A for ; Thu, 8 Sep 2016 18:32:00 +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 u88IW0LN066326 for ; Thu, 8 Sep 2016 18:32:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 212494] www/chromium: doesn't render properly Date: Thu, 08 Sep 2016 18:32:00 +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: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cpm@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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, 08 Sep 2016 18:32:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212494 Carlos J. Puga Medina changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-ports-bugs@FreeBSD. |chromium@FreeBSD.org |org | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-chromium@freebsd.org Thu Sep 8 19:07:49 2016 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 1AF99BD2D97 for ; Thu, 8 Sep 2016 19:07:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 049BE779 for ; Thu, 8 Sep 2016 19:07:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 00A8ABD2D96; Thu, 8 Sep 2016 19:07:49 +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 0055EBD2D95 for ; Thu, 8 Sep 2016 19:07:49 +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 E42AC777 for ; Thu, 8 Sep 2016 19:07:48 +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 u88J7mHY082122 for ; Thu, 8 Sep 2016 19:07:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 212494] www/chromium: doesn't render properly Date: Thu, 08 Sep 2016 19:07:49 +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: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cperciva@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc bug_status resolution 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, 08 Sep 2016 19:07:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212494 Colin Percival changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cperciva@FreeBSD.org Status|New |Closed Resolution|--- |DUPLICATE --- Comment #1 from Colin Percival --- *** This bug has been marked as a duplicate of bug 212060 *** --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-chromium@freebsd.org Thu Sep 8 19:07:49 2016 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 F04E4BD2D9B for ; Thu, 8 Sep 2016 19:07:49 +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 D99B577E for ; Thu, 8 Sep 2016 19:07:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D90F6BD2D9A; Thu, 8 Sep 2016 19:07:49 +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 D8C0FBD2D99 for ; Thu, 8 Sep 2016 19:07:49 +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 C5E5B77D for ; Thu, 8 Sep 2016 19:07:49 +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 u88J7mHe082122 for ; Thu, 8 Sep 2016 19:07:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 212060] www/chromium: crippled tabs+url bar in 52.0.x version Date: Thu, 08 Sep 2016 19:07:49 +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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cperciva@FreeBSD.org X-Bugzilla-Status: New 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, 08 Sep 2016 19:07:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212060 Colin Percival changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |owen94012@gmail.com --- Comment #2 from Colin Percival --- *** Bug 212494 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-chromium@freebsd.org Fri Sep 9 11:06:27 2016 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 7FE3ABD4F72 for ; Fri, 9 Sep 2016 11:06:27 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4228B938 for ; Fri, 9 Sep 2016 11:06:27 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from karviainen.kapsi.fi ([217.30.184.182] helo=roundcube.kapsi.fi) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1biJdV-0000Xj-Jc; Fri, 09 Sep 2016 14:06:22 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 09 Sep 2016 14:06:21 +0300 From: Arto Pekkanen To: clutton Cc: freebsd-chromium In-Reply-To: <1472985750.17294.22.camel@zoho.com> References: <1471486169.7533.8.camel@zoho.com> <1472667320.8146.46.camel@zoho.com> <1d42dcb1faf8cbe4fbf24066a4163134@kapsi.fi> <1472985750.17294.22.camel@zoho.com> Message-ID: <732bbbfa1ca6903e0f76e4f98a955a28@kapsi.fi> X-Sender: isoa@kapsi.fi User-Agent: RoundCube Webmail/0.9.4 X-SA-Exim-Connect-IP: 217.30.184.182 X-SA-Exim-Mail-From: isoa@kapsi.fi X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail X-Spam-Level: X-Spam-Status: No, score=-4.6 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.2 Subject: Re: 52.0.2743.82 (64-bit) to go, Aw snap is still there X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mail.kapsi.fi) 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: Fri, 09 Sep 2016 11:06:27 -0000 Cool! Thanks for the info. Now I know where we're going with the project. I suppose we will see later how the collaboration with upstream goes. Awesome work with GN/ninja btw, that will help a lot in the future! clutton kirjoitti 04.09.2016 13:42: > On Sun, 2016-09-04 at 02:30 +0300, Arto Pekkanen wrote: >> So I was right from the very start: the Chromium codebase assumes  >> certain behaviour from the memory allocation API of the host system, >> and  >> if this behavour is not in line with Linux (and Android), then >> problems  >> are to be expected. Yeah. Yet another fine example of how Open Source >> is  >> becoming synonymous with "Designed for Linux". >> >> Is there any hope to get these changes propagated upstream to >> Chromium  >> developers? >> >> It would be really nice to have upstream collaboration, because if >> the  >> upstream yet again changes things ever so slightly, things will  >> mysteriously break. > > No, you wasn't right about the memory. I just wrote - base allocator > works fine. Their home-brew assembler snippets work fine. I haven't > checked blink allocator as thoroughly as base, may be it's there > something not right. Do not assume that chromium is bug-free also. > Some shit may fire with conditions met. > > For now I have GN ninja fully working (I believe I'll commit today), I > doubt that google would take it upstream, such a mess to add another > architecture. Nevertheless - I'm using macros is_bsd, with assumption > that code would use OS_BSD, and with some division > OS_OPENBSD/OS_FREEBSD further in C/C++ code, so it's more clean and has > more chances to be accepted. But may no mistake - they invest a lot of > resources to make this chrome work according to a plan, I don't think > that they would add another OS. Unless there are a lot of people > interested. > > About Linuxism, - they divide code very simple, if you don't like the > functionality, you can rewrite it for your OS... The thing is - we use > a lot of code written for Linux. > > >> clutton kirjoitti 31.08.2016 21:15: >> > >> > On Thu, 2016-08-18 at 05:09 +0300, clutton wrote: >> > > >> > > I've just fixed the Aw, snap. I believe so. >> > Ok, time to admit the defeat. I haven't fixed the issue in time, >> > and I >> > planned to do so till the summer is there. Being to much arrogant I >> > started just before the end of time. I still can't believe I >> > haven't >> > fixed this in time. >> > >> > I'll work on this, but not so intensively, now I just can't left >> > it. >> > I learned about the codebase so much. And all those small >> > improvements >> > shouldn't be wasted anyway (I haven't posted any because they worth >> > nothing without fixing the bug). I'll do it more slowly and >> > considerably now. >> > >> > Number 1 issue is to bring new gn ninja generation system, every >> > documentation assumes that you use gn, in future they will remove >> > gyp >> > generator. It would be much easier to work then. >> > Number 2 is probably to clean the mess in our pathes. >> > >> > Some thoughts for maintainers/developers: >> > >> > Don't try debugging if you don't have enough RAM, I distributed the >> > compilation to distcc, but RAM was an issue, even with another ssd >> > attached as a swap it was tooooo slow to work with debugger, I did >> > a >> > lot of tricks to make it possible though, And have a lot of >> > frustrations when those tricks mangle the code. I wish I could just >> > put >> > that monster in RAM press bt and don't wait 5 minutes till it's >> > done. >> > >> > Memory allocation in base works fine, I might missed something but >> > debugging bit after bit was fine, then I finally did stubs, then I >> > finally found that new shim allocator have those stubs already, >> > some >> > fixes would be needed though, for now I used this: >> > allocator_shim_default_dispatch_to_libc.cc >> > extern "C" { >> > void* __malloc(size_t size); >> > void* __calloc(size_t n, size_t size); >> > void* __realloc(void* address, size_t size); >> > void* __memalign(size_t alignment, size_t size) { >> >   void *ret; >> >   if (__posix_memalign(&ret, alignment, size) != 0) { >> >     return nullptr; >> >   } else { >> >     return ret; >> >   } >> > } >> > int  __posix_memalign(void **ptr, size_t alignment, size_t size); >> > void __free(void* ptr); >> > }  // extern "C" >> > >> > But they assume linux and android, and they implement >> > posix_memalign >> > through memalign, I did the opposite. For now I have that >> > unnecessary >> > chain. It works but it could work faster without chain. >> > >> > I haven't debugged heavily blink memory allocator, which I should >> > have >> > done instead of base allocator... There are some approaches to make >> > it >> > not to crush, but they are just hardcode patching, not fixing. And >> > some >> > patches I thought work just delaying the freezing. >> > >> > Next, chromium team patch libraries, those in third_party >> > directory, I >> > debugged some of them, seems fine. No difference in work comparing >> > to >> > our. But that is probably is something to look at more. Ninja >> > sucks, >> > once I put the most recent re2 library by mistake and ninja >> > compiled it >> > without hesitation. Then I had coredumps on that library. >> > >> > >> > Ok, probably all, because writing everything would be to much for >> > non >> > prepared reader. Better send patches. "Talk is cheap. Show me the >> > code" -- Arto Pekkanen From owner-freebsd-chromium@freebsd.org Sat Sep 10 02:53:15 2016 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 84144BD4317 for ; Sat, 10 Sep 2016 02:53:15 +0000 (UTC) (envelope-from bounce-mc.us8_27708099.1182165-freebsd-chromium=freebsd.org@mail64.atl111.rsgsv.net) Received: from mail64.atl111.rsgsv.net (mail64.atl111.rsgsv.net [198.2.131.64]) by mx1.freebsd.org (Postfix) with ESMTP id 5BDC1DDB for ; Sat, 10 Sep 2016 02:53:15 +0000 (UTC) (envelope-from bounce-mc.us8_27708099.1182165-freebsd-chromium=freebsd.org@mail64.atl111.rsgsv.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=k1; d=mail64.atl111.rsgsv.net; h=Subject:From:Reply-To:To:Date:Message-ID:List-ID:List-Unsubscribe:Sender:Content-Type; i=insidersclub=3Dyellowbirdestatesales.com@mail64.atl111.rsgsv.net; bh=Asa9M0nZrmpXVyRa68a3T8HdxpE=; b=ANAK4IldSZahIhFrLmWnqNjRtpW+vPx2ZB6N9kKwhOYu+crKeZTDr5siCREwdhfcl6qZ8FJFJUts gzwbTYDr8geMD4Obt+qSMshZyxEXtQlPa3IQx+EOWFMcsG8wotUQ4ZEplNthTI/BhPwHuQ9HoACh uvxhyzg8kJmIQ3XpW0o= Received: from (127.0.0.1) by mail64.atl111.rsgsv.net id hqdqpm1ohlgu for ; Sat, 10 Sep 2016 02:38:07 +0000 (envelope-from ) Subject: =?utf-8?Q?A=20Slow=20Friday=20Means=20You=27re=20the=20Winner=20on=20Saturday?= From: =?utf-8?Q?Yellow=20Bird=20Estate=20Sales?= Reply-To: =?utf-8?Q?Yellow=20Bird=20Estate=20Sales?= To: Date: Sat, 10 Sep 2016 02:38:07 +0000 Message-ID: <4e56a67f969cbc6571f2e4d4bee009d5e19.20160910023745@mail64.atl111.rsgsv.net> X-Mailer: MailChimp Mailer - **CID4da0ef3fd7ee009d5e19** X-Campaign: mailchimp4e56a67f969cbc6571f2e4d4b.4da0ef3fd7 X-campaignid: mailchimp4e56a67f969cbc6571f2e4d4b.4da0ef3fd7 X-Report-Abuse: Please report abuse for this campaign here: http://www.mailchimp.com/abuse/abuse.phtml?u=4e56a67f969cbc6571f2e4d4b&id=4da0ef3fd7&e=ee009d5e19 X-MC-User: 4e56a67f969cbc6571f2e4d4b X-Feedback-ID: 27708099:27708099.1182165:us8:mc X-Accounttype: pd Sender: "Yellow Bird Estate Sales" x-mcda: FALSE Content-Type: text/plain; charset="us-ascii" 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: Sat, 10 Sep 2016 02:53:15 -0000 --- It's 50% off Saturday Friday was slow so you're the Big Winner with lots of Tools, Wood, Antiques, Collectables, Toys Jewelry, Watches, A 1949 or 1950 Farm All Tractor with Implements, and Much Much More. 1774 Bolton Circle Norcross, GA 30071 Sale Hours: 8:30 to 2:00 visit www.yellowbirdestatesale.com to view pictures.--- ============================================== *|Yellow Bird Insiders Club|* Unsubscribe *|insidersclub@yellowbirdestatesales.com|* from this list: http://yellowbirdestatesales.us8.list-manage.com/unsubscribe?u=4e56a67f969cbc6571f2e4d4b&id=8a6f15cd2d&e=ee009d5e19&c=4da0ef3fd7 Our mailing address is: *[insidersclub@yellowbirdestatesales.com|* Forward this email to a friend: http://us8.forward-to-friend1.com/forward?u=4e56a67f969cbc6571f2e4d4b&id=4da0ef3fd7&e=ee009d5e19 Update your profile: http://yellowbirdestatesales.us8.list-manage.com/profile?u=4e56a67f969cbc6571f2e4d4b&id=8a6f15cd2d&e=ee009d5e19