[chromium-dev] Re: buildbot off line tonight
Sounds interesting... how did you implement size tracking? Just looking at the size of chrome.dll or the total zip or ...? Mozilla has a very nice tool that shows the delta for each symbol in each binary. It is very helpful for understand where code size changes come from. Some info: https://wiki.mozilla.org/Codesighs -Darin On Thu, Apr 16, 2009 at 4:16 PM, Steven Knight wrote: > Heads up: > > I'd like to take the buildbot off line tonight, ~22:00 PDT, to add size > tracking to the release builders. It should not be down long. Let me know > if that would interfere with any plans you have. > > Thanks, > > --SK > > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Try server issues today
You may have realized that the try server has started merging unrelated jobs in one run. What a time saving feature! It seems to be a side-effect of a change I've introduced today and I'll fix this ASAP, e.g. tomorrow. :) Before anyone starts running with a pitch fork, let me show you this: http://codereview.chromium.org/63137 (and yes, the box color is still wrong, it should be green; shout out to mad@ for the rietveld change) Thanks for bearing with me, M-A --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] buildbot off line tonight
Heads up: I'd like to take the buildbot off line tonight, ~22:00 PDT, to add size tracking to the release builders. It should not be down long. Let me know if that would interfere with any plans you have. Thanks, --SK --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Building Chromium and running on Fedora 10
Also, can you verify that you have msttcorefonts installed in /usr/share/fonts/truetype/msttcorefonts? It's likely that the renderers are crashing because they can't find the required fonts. On Thu, Apr 16, 2009 at 12:04 PM, Adam Langley wrote: > > On Thu, Apr 16, 2009 at 11:34 AM, rrwinterton > wrote: > > I have build and ran the latest (10 Apr 09) source on Ubuntu. I then > > tried to build and run it on Fedora 10. I was successful in building > > it but when I ran the binary the browser came up but the chromium > > splash did not show up and I was unable to browse to different sites. > > I believe it is a rendering problem due to incorrect links. Does > > anyone have any suggestions on how to get a correct build with the > > correct libraries on Fedora? > > We have a working build on Fedora. Tony might be able to give you more > details. > > It sounds like the renderer is crashing. If you build a debug version > you can run: > chrome --renderer-cmd-prefix="xterm -e gdb --args" > > to start the renderer in GDB and catch the crash. > > > AGL > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: localStorage design document - please offer feedback!
On Tue, Apr 14, 2009 at 9:32 AM, Darin Fisher wrote: > Please ask Brett Wilson to review your DB schema and operations. > Brett, can you please take a look? The database part of it is towards the end of the page. http://docs.google.com/a/chromium.org/Doc?id=dhs4g97m_1v79p3wdd&hl=en --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] chrome code size source lines
I don't know if anyone's already done this, but I figured I'd share the results in case anyone was curious. I'm using j...@google.com's script for parsing objdump output and sorting it. These results are generated by building a Release mode chrome with "-g2" added to get the line numbers. This is built with gcc on linux with a tree checked out two days ago or so. No surprise, but stl code figures prominently here. Looks like the webkit ref counting and containers also show up. [Column 1: Bytes per occurrence] [Column 2: Total bytes of generated code] [Column 3: Number of occurrences] [Column 4: Actual source file & line number] 30.5 34280211223 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/RefCounted.h:94 18.0 22174612310 /usr/include/c++/4.2/bits/basic_string.h:238 8.3 16937120511 /usr/include/c++/4.2/bits/basic_string.h:234 9.7 16848817451 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/RefCounted.h:67 29.7 155668 5236 /usr/include/c++/4.2/ostream:517 15.5 143931 9289 /usr/local/google/chromium4/src/third_party/WebKit/WebCore/platform/TreeShared.h:65 30.0 142957 4771 /usr/include/c++/4.2/ext/atomicity.h:51 8.1 12486915454 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/RefPtr.h:50 11.0 12029010931 /usr/include/c++/4.2/ext/atomicity.h:83 5.79852917262 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/RefCounted.h:74 7.27898710931 /usr/include/c++/4.2/bits/basic_string.h:236 6.57462211474 /usr/include/c++/4.2/bits/basic_string.h:288 20.872263 3481 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/Vector.h:462 13.671845 5284 /usr/local/google/chromium4/src/third_party/WebKit/WebCore/platform/TreeShared.h:69 13.068506 5283 /usr/local/google/chromium4/src/v8/include/v8.h:191 6.06587710931 /usr/include/c++/4.2/ext/atomicity.h:70 40.463852 1581 /usr/local/google/chromium4/src/webkit/port/bindings/v8/v8_proxy.h:366 36.450688 1392 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/HashTable.h:422 10.546967 4470 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/RefPtr.h:39 17.542025 2401 /usr/local/google/chromium4/src/third_party/icu38/public/common/unicode/unistr.h:3311 20.540907 2000 /usr/local/google/chromium4/src/v8/include/v8.h:2437 3.13407610910 /usr/include/c++/4.2/ext/atomicity.h:69 25.633080 1291 /usr/include/c++/4.2/bits/stl_vector.h:88 19.031160 1640 /usr/local/google/chromium4/src/v8/include/v8.h:240 18.130243 1674 /usr/local/google/chromium4/src/v8/include/v8.h:239 24.629691 1208 /usr/local/google/chromium4/src/third_party/WebKit/WebCore/svg/SVGDocumentExtensions.h:72 31.729620 933 /usr/local/google/chromium4/src/third_party/WebKit/WebCore/platform/KURLGooglePrivate.h:47 17.828586 1603 /usr/local/google/chromium4/src/webkit/port/bindings/v8/v8_proxy.h:494 16.025090 1566 /usr/include/c++/4.2/bits/basic_string.h:491 4.124803 6057 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/RefCounted.h:37 20.824332 1170 /usr/local/google/chromium4/src/third_party/WebKit/WebCore/svg/SVGAnimatedTemplate.h:120 16.723587 1414 /usr/local/google/chromium4/src/base/ref_counted.h:107 12.823532 1840 /usr/include/c++/4.2/bits/stl_algobase.h:187 28.823288 810 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/HashTable.h:323 33.222721 685 /usr/local/google/chromium4/src/v8/src/zone-inl.h:45 4.922286 4594 /usr/local/google/chromium4/src/third_party/WebKit/JavaScriptCore/wtf/RefPtr.h:54 28.122084 785 /usr/include/c++/4.2/iostream:77 For perspective: willc...@panda:/usr/local/google/chromium4/src$ size sconsbuild/Release/chrome textdata bss dec hex filename 175305398458168 122180 2611088718e6ba7 sconsbuild/Release/chrome So the text segment is 16.7MB. RefCounted.h:94 contributes to 2% of the code size. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Building Chromium and running on Fedora 10
On Thu, Apr 16, 2009 at 11:34 AM, rrwinterton wrote: > I have build and ran the latest (10 Apr 09) source on Ubuntu. I then > tried to build and run it on Fedora 10. I was successful in building > it but when I ran the binary the browser came up but the chromium > splash did not show up and I was unable to browse to different sites. > I believe it is a rendering problem due to incorrect links. Does > anyone have any suggestions on how to get a correct build with the > correct libraries on Fedora? We have a working build on Fedora. Tony might be able to give you more details. It sounds like the renderer is crashing. If you build a debug version you can run: chrome --renderer-cmd-prefix="xterm -e gdb --args" to start the renderer in GDB and catch the crash. AGL --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Building Chromium and running on Fedora 10
Hi, I have build and ran the latest (10 Apr 09) source on Ubuntu. I then tried to build and run it on Fedora 10. I was successful in building it but when I ran the binary the browser came up but the chromium splash did not show up and I was unable to browse to different sites. I believe it is a rendering problem due to incorrect links. Does anyone have any suggestions on how to get a correct build with the correct libraries on Fedora? Thanks in advance. Rich --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
