Re: [webkit-dev] How to implement an API taking int or float array as function arguments?

Generally, that's not really possible in WebKit. If you look around, you'll find some hacky examples, but this feature of WebIDL isn't supported by our code generator and is flux in WebIDL proper. If there's a specific API you're having trouble implementing, I'd recommend changing the API to not

[webkit-dev] How to implement an API taking int or float array as function arguments?

Hi all, I'm looking for a good example of how to implement an API in IDL and source code in WebCore, which takes integer or float array as function arguments from JavaScript. I appreciate your help. Regards, Won ___ webkit-dev mailing list webkit-dev@li

Re: [webkit-dev] SnowLeopard debug buildbot not there

All these inspector's crashes were introduced at r80478 They were not detected immediately because: 1) the noncore Intel Leopard Debug Test box are constantly red; 2) most of the time it has a problem with svn; 3) the box was offline? for a week from mar 1 to mar 8. (~800 patches) Patch was rolle

Re: [webkit-dev] SnowLeopard debug buildbot not there

On Mar 10, 2011, at 3:51 PM, Adam Roben wrote: I'm also planning to file a bug about CoreText-related leaks beneath GlyphPage::fill. CoreText-related leaks seen beneath GlyphPage::fill -Adam ___ webkit-dev mailing li

Re: [webkit-dev] SnowLeopard debug buildbot not there

On Thu, Mar 10, 2011 at 12:48 PM, Adam Roben wrote: > On Mar 10, 2011, at 3:40 PM, Adam Barth wrote: >> On Thu, Mar 10, 2011 at 12:33 PM, Mark Rowe wrote: >>> On 2011-03-10, at 12:27, Adam Barth wrote: On Thu, Mar 10, 2011 at 12:11 PM, Mark Rowe wrote: > On 2011-03-10, at 12:08, David L

Re: [webkit-dev] SnowLeopard debug buildbot not there

By the way, I've been starting to look at leaks a little bit lately. I've filed these so far: REGRESSION (r79817): Lots of leaks of FloatingObjects seen on SnowLeopard Intel Leaks bot <-- this one has been fixed Many leaks seen be

Re: [webkit-dev] SnowLeopard debug buildbot not there

On Mar 10, 2011, at 3:40 PM, Adam Barth wrote: On Thu, Mar 10, 2011 at 12:33 PM, Mark Rowe wrote: On 2011-03-10, at 12:27, Adam Barth wrote: On Thu, Mar 10, 2011 at 12:11 PM, Mark Rowe wrote: On 2011-03-10, at 12:08, David Levin wrote: tL;dr "Why isn't there a SnowLeopard debug buildbot? R

Re: [webkit-dev] SnowLeopard debug buildbot not there

On 2011-03-10, at 12:40, Adam Barth wrote: > On Thu, Mar 10, 2011 at 12:33 PM, Mark Rowe wrote: >> On 2011-03-10, at 12:27, Adam Barth wrote: >>> On Thu, Mar 10, 2011 at 12:11 PM, Mark Rowe wrote: On 2011-03-10, at 12:08, David Levin wrote: > tL;dr "Why isn't there a SnowLeopard debug

Re: [webkit-dev] SnowLeopard debug buildbot not there

On Thu, Mar 10, 2011 at 12:33 PM, Mark Rowe wrote: > On 2011-03-10, at 12:27, Adam Barth wrote: >> On Thu, Mar 10, 2011 at 12:11 PM, Mark Rowe wrote: >>> On 2011-03-10, at 12:08, David Levin wrote: tL;dr "Why isn't there a SnowLeopard debug buildbot? Related: Why does the commit queue

Re: [webkit-dev] SnowLeopard debug buildbot not there

On 2011-03-10, at 12:27, Adam Barth wrote: > On Thu, Mar 10, 2011 at 12:11 PM, Mark Rowe wrote: >> On 2011-03-10, at 12:08, David Levin wrote: >>> tL;dr "Why isn't there a SnowLeopard debug buildbot? Related: Why does the >>> commit queue (appear) to only run release builds through tests?" >>>

Re: [webkit-dev] SnowLeopard debug buildbot not there

On Thu, Mar 10, 2011 at 12:11 PM, Mark Rowe wrote: > On 2011-03-10, at 12:08, David Levin wrote: >> tL;dr "Why isn't there a SnowLeopard debug buildbot? Related: Why does the >> commit queue (appear) to only run release builds through tests?" >> >> Details: >> Yesterday, I did a build of WebKit o

Re: [webkit-dev] SnowLeopard debug buildbot not there

The commit-queue runs release for two reasons: 1) It's faster. 2) Most developers build/test debug. Having the commit-queue build release covers one more base. Now that we have a cluster of commit-queue machines, we could probably build and test both debug and release. Adam On Thu, Mar 10, 20

Re: [webkit-dev] SnowLeopard debug buildbot not there

On 2011-03-10, at 12:08, David Levin wrote: > tL;dr "Why isn't there a SnowLeopard debug buildbot? Related: Why does the > commit queue (appear) to only run release builds through tests?" > > Details: > Yesterday, I did a build of WebKit on SnowLeopard and hit ~12 crashes (mostly > in inspecto

[webkit-dev] SnowLeopard debug buildbot not there

tL;dr "Why isn't there a SnowLeopard debug buildbot? Related: Why does the commit queue (appear) to only run release builds through tests?" Details: Yesterday, I did a build of WebKit on SnowLeopard and hit ~12 crashes (mostly in inspector tests). Then I realized that we don't have such a bot, so

Re: [webkit-dev] Webkit handling of plug-ins out-of-process on the mac

One of the specifics is: is there a separate process for each object/document controlled by a given plug-in, or are all objects controlled by that plug-in in the same extra process, or is it a mix? On Mar 9, 2011, at 10:08 PM, Sam Weinig wrote: WebKit has had the ability to run plugins out of p

Re: [webkit-dev] Building WebKit's GTK+ back-end using distcc timing

Hi, >> additional reasons why it is taking so much time now, but I would point >> to pre-processing and linking as possible causes for the distcc master >> now doing more work. I would rule out the linking phase as being the bottleneck: this is happening at the end of the process. I've eventually

Re: [webkit-dev] Building WebKit's GTK+ back-end using distcc timing

As far as I know, distcc master process pre-processes the code before sending it to the slaves. Having more (or bigger) files in the tree could be the cause of your master machine having to do more work before offloading the compilation to the slaves. Last, but not least, more code means more wo

Re: [webkit-dev] Building WebKit's GTK+ back-end using distcc timing

Hi Ilyes, On Thu, 10 Mar 2011 13:51:48 +0100 Ilyes Gouta wrote: > I don't think that the slowdown is due to the addition of new > C++/code. Even building with most of the WebKit options turned off, > actually takes that much of time. > > By just observing how the files are dispatched to the di

Re: [webkit-dev] Building WebKit's GTK+ back-end using distcc timing

Hi Alejandro, I don't think that the slowdown is due to the addition of new C++/code. Even building with most of the WebKit options turned off, actually takes that much of time. By just observing how the files are dispatched to the distcc servers, how these are loaded by the client machine (which

Re: [webkit-dev] Building WebKit's GTK+ back-end using distcc timing

On Thu, Mar 10, 2011 at 11:55:15AM +0100, Ilyes Gouta wrote: > Hi, > > [...] > > Could some one enlighten us about what have changed in the build > system of the Gtk+ port of WebKit that would have an impact on the > total build time? Could it be that configure.ac has changed so that > the final

[webkit-dev] Building WebKit's GTK+ back-end using distcc timing

Hi, We've got a distcc setup/environment where we're used to build WebKit Gtk+, a rather an old code base (WebKit.org corresponding commit 9161f3277b15aae8d15a929d5362e28cad7e01c0) compared to the current WebKit's trunk and the thing is that we could achieve a complete build in about 22 min or so,