On Mon, Nov 30, 2009 at 9:37 AM, Chris Bentzel cbent...@google.com wrote:
When DCHECK's trigger on my debug chromium build, I get an unsymbolized
stacktrace like
[7036:25234:31462940569:FATAL:net/ocsp/nss_ocsp.cc(251)] Check failed:
!request_.
On Tue, Oct 27, 2009 at 9:10 PM, Mike Belshe mbel...@google.com wrote:
On Tue, Oct 27, 2009 at 3:24 PM, Jens Alfke s...@chromium.org wrote:
Do we plan to switch the Mac build of Chromium to use tcmalloc instead of
the system malloc? I thought this was the case, but I can't find any bug
w00t, nice job.
On Thu, Aug 20, 2009 at 8:44 AM, Dean McNameede...@chromium.org wrote:
The v8 team did some amazing work this quarter building a working
64-bit port. After a handful of changes on the Chromium side, I've
had Chromium Linux building on 64-bit for the last few weeks. I
On Thu, Aug 20, 2009 at 10:26 AM, Evan Martine...@chromium.org wrote:
How does the v8 perf look like relative to 32-bit?
I guess we ought to set up perf bots for startup/memory/etc. as well;
I'd expect we improve on those metrics on our 64-bit buildbots due to
more sharing with other apps
printing_unittests depends on gtestmain.lib. See src/printing/printing.gyp.
On Wed, Jun 24, 2009 at 12:46 AM, Jickae Davisjick...@gmail.com wrote:
yep, for base_unittests, that's true.
But what I want to know is how chromium uses GTest. An important problem is
how it runs all the GTest
sorry to evanerg for the remail, my @google.com one bounced
Hi,
I dunno what's up, but git isn't sync'ing to the latest svn revisions for me:
(21:37:35) willchan: any git experts around?
(21:37:35) mdengfeng left the room (quit: Read error: 104
On Tue, May 19, 2009 at 5:12 PM, James Hawkins jhawk...@chromium.org wrote:
On Tue, May 19, 2009 at 5:07 PM, Evan Stade est...@chromium.org wrote:
Are we sure we need this functionality? I understand the intention of
seeing when we're not drawing fast enough, but I'm seeing the green
, 2009 at 4:49 PM, William Chan (陈智昌)
willc...@chromium.org wrote:
My old team never really used FRIEND_TEST. We found it ugly that our
production code depended on test code. We typically used friended
Peer classes defined in the unittest file, but not in the anonymous
namespace
My old team never really used FRIEND_TEST. We found it ugly that our
production code depended on test code. We typically used friended
Peer classes defined in the unittest file, but not in the anonymous
namespace. These are simple shims that provide access to the private
section. It also
, 2009 at 11:21 PM, Adam Langley a...@chromium.org wrote:
On Wed, Feb 25, 2009 at 1:13 PM, William Chan (陈智昌)
willc...@chromium.org wrote:
I talked to Darin and he told me that this needs work since it's
impacting the page cycler times, so I figured I'd pick it up. You
have a TODO
Hey Dean,
I talked to Darin and he told me that this needs work since it's
impacting the page cycler times, so I figured I'd pick it up. You
have a TODO there saying to figure out how to best do async IO. Did
you ever figure this out? I talked to Darin briefly and decided that
the simplest
Woops, newbie mistake, sent from my google.com addr the first time.
2009/2/25 William Chan (陈智昌) willc...@google.com:
Sorry for not being clear. Yep, you're correct, I'm not planning use
POSIX async IO. Just planning to execute the sync IO on the
WorkerPool.
On Wed, Feb 25, 2009 at 1:21
12 matches
Mail list logo
