Thomas Van Lenten wrote:
Where are the profile dirs going on disk? Time machine doesn't have to be
on, we can add things to this file incase it is turned on.
(and again. the multiple-address interface for mailing lists kind of sucks.)
--
Chromium Developers mailing list:
tl;dr I just landed a change that may improve drawing performance.
Because the code path depends on the machine, it is difficult to test
that I didn't break anything. Please let me know if you notice a
drawing speed difference in Chrome builds after r35390/35392 (latter
was a build fix for the
On Wed, Dec 30, 2009 at 3:02 PM, Chris Evans cev...@google.com wrote:
I'm interested in a breakdown here. Is it dependent on X server version?
(e.g. can you say Ubuntu version 9.10+ has it)? Or is it more subtle,
involving exact gfx chipset and proprietary vs. X.org drivers?
The latter, I
On Wed, Dec 30, 2009 at 3:21 PM, Evan Martin e...@chromium.org wrote:
On Wed, Dec 30, 2009 at 3:02 PM, Chris Evans cev...@google.com wrote:
I'm interested in a breakdown here. Is it dependent on X server version?
(e.g. can you say Ubuntu version 9.10+ has it)? Or is it more subtle,
involving
On Wed, Dec 30, 2009 at 3:43 PM, Peter Kasting pkast...@google.com wrote:
On Wed, Dec 30, 2009 at 3:22 PM, Jeremy Orlow jor...@google.com wrote:
I just got back from vacation and would like to take action on this. I
read through the thread, but I don't see any sort of consensus on what to
On Wed, Dec 30, 2009 at 3:56 PM, Jeremy Orlow jor...@google.com wrote:
2) Info bar. This seems like one of the more popular options at the
moment.
This is a bad idea, we shouldn't do it. It's not as annoying as a modal
dialog, it has problems with clashing with other infobars on start.
I thought there were two separate issues here:
1.) The specific webgl switch. Darin suggested that it should imply
--disable-sandbox until webgl works in the sandbox. This way, people
don't have to add --disable-sandbox explicitly and will automatically
be safe once webgl works in the sandbox.
On Wed, Dec 30, 2009 at 4:15 PM, Nico Weber tha...@chromium.org wrote:
I thought there were two separate issues here:
1.) The specific webgl switch. Darin suggested that it should imply
--disable-sandbox until webgl works in the sandbox. This way, people
don't have to add --disable-sandbox
Automatically closing tree for net_unittests on Modules XP (dbg)
http://build.chromium.org/buildbot/waterfall/builders/Modules%20XP%20%28dbg%29/builds/21091
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Modules%20XP%20%28dbg%29
--= Automatically closing tree for net_unittests
Your log seems fine so it's probably not the Avi/Trung/breakpad bug.
I'm not aware of any case where Chrome launches 'ps' other than about:memory
(Mac only). Some quick tests with about:memory on 249.30 do not create ps
zombies. I could not see any obvious path in base/process_util_posix.cc's
On Wed, Dec 30, 2009 at 10:42 PM, John Grabowski j...@chromium.org wrote:
Your log seems fine so it's probably not the Avi/Trung/breakpad bug.
I'm not aware of any case where Chrome launches 'ps' other than
about:memory (Mac only). Some quick tests with about:memory on 249.30 do
not create
Hi,
Can you please tell me how does make determine which files to compile
in chromium?
I add a test.cc file under chrome/browser, and then do 'make
out/Debug/chrome' again, but nothing is compiled.
I have looked for *.mk file to find the list of files to compile, but
nothing like that is there.
Project files (Make, Visual Studios, and Xcode) are all generated from GYP
(Generate Your Projects). These are the .gyp and .gypi files in the source
directories. For chrome/browser/, look at
chrome/browser/chrome_browser.gypi.
rsesek / @chromium.org
On Wed, Dec 30, 2009 at 8:55 PM, hap 497
Debugging tips:
1. What's the parent pid of your zombies? Is it a browser process or
something else?
2. Temporarily move /bin/ps to /bin/ps.real, and at /bin/ps put a
small script that writes the full argument list and maybe other
debuggery to a log file somewhere, and then invokes
On Wed, Dec 30, 2009 at 7:42 PM, John Grabowski j...@chromium.org wrote:
Your log seems fine so it's probably not the Avi/Trung/breakpad bug.
I'm not aware of any case where Chrome launches 'ps' other than
about:memory (Mac only). Some quick tests with about:memory on 249.30 do
not create
Viet-Trung Luu wrote:
2. Temporarily move /bin/ps to /bin/ps.real, and at /bin/ps put a
small script that writes the full argument list and maybe other
debuggery to a log file somewhere, and then invokes /bin/ps.real. For
example:
[...]
Done. And I now see that it looks like my fault. Now I
The default max procs per userid on 10.5.8 is 266. With ~20 Chromes and
10 tabs each you're starting to get real close. Perhaps that's the real
problem?
That's a fair reasoning but then it should have been so all along. And I
reach the same state even with 10 chrome instances, only it
17 matches
Mail list logo
