On Fri, Jul 08, 2011 at 02:46:20PM -0500, Marco Peereboom wrote:
> This seems to be fixable by doing something like this:
> --- Source/WebCore/platform/graphics/FontFallbackList.cpp.origFri Jul
> 8 14:05:45 2011
> +++ Source/WebCore/platform/graphics/FontFallbackList.cpp Fri Jul 8
>
https://bugs.webkit.org/show_bug.cgi?id=64355
On Mon, Jul 11, 2011 at 12:16:28PM +1200, Gavin Lambert wrote:
> Quoth Marco Peereboom:
> > So I found the bug that causes this however I do not have a patch.
> > What happens is that in my browser I set max-conns and max-conns-per-host
> > right after
Quoth Marco Peereboom:
> So I found the bug that causes this however I do not have a patch.
> What happens is that in my browser I set max-conns and max-conns-per-host
> right after obtaining the default session. Like so:
>
> session = webkit_get_default_session();
> g_object_set(sess
On Thu, Jun 30, 2011 at 09:54:34AM -0500, Marco Peereboom wrote:
> On Wed, Jun 29, 2011 at 06:27:30PM -0500, Marco Peereboom wrote:
> > On Wed, Jun 29, 2011 at 04:23:00PM -0700, Martin Robinson wrote:
> > > On Wed, Jun 29, 2011 at 2:43 PM, Marco Peereboom
> > > wrote:
> > >
> > > > This is with
On Thu, Jun 30, 2011 at 09:54:34AM -0500, Marco Peereboom wrote:
> On Wed, Jun 29, 2011 at 06:27:30PM -0500, Marco Peereboom wrote:
> > On Wed, Jun 29, 2011 at 04:23:00PM -0700, Martin Robinson wrote:
> > > On Wed, Jun 29, 2011 at 2:43 PM, Marco Peereboom
> > > wrote:
> > >
> > > > This is with
On Wed, Jun 29, 2011 at 06:27:30PM -0500, Marco Peereboom wrote:
> On Wed, Jun 29, 2011 at 04:23:00PM -0700, Martin Robinson wrote:
> > On Wed, Jun 29, 2011 at 2:43 PM, Marco Peereboom wrote:
> >
> > > This is with the webkit 1.4.1 snapshot with web sockets enabled. ??By
> > > default xxxterm set
On Wed, Jun 29, 2011 at 04:23:00PM -0700, Martin Robinson wrote:
> On Wed, Jun 29, 2011 at 2:43 PM, Marco Peereboom wrote:
>
> > This is with the webkit 1.4.1 snapshot with web sockets enabled. ??By
> > default xxxterm sets max-conns to 25 and max-conns-per-host to 5. ??When
> > webkit doesn't cr
On Wed, Jun 29, 2011 at 2:43 PM, Marco Peereboom wrote:
> This is with the webkit 1.4.1 snapshot with web sockets enabled. By
> default xxxterm sets max-conns to 25 and max-conns-per-host to 5. When
> webkit doesn't crash I see as many as 119 connections to port 80 in
> various states (TIME_WAI
Ok I captured a few screenshots to illustrate what I see and some
backtraces as well when I push file descriptors well past starvation.
The test I run is always the same. I open a session which in the
xxxterm browser means "an X number of tabs with links in them". The
links are:
https://www.cyphe
En 27/06/11 18:30, Marco Peereboom escribiu:
> On Mon, Jun 27, 2011 at 12:19:08PM -0400, Dan Winship wrote:
>> On 06/24/2011 04:49 PM, David Hill wrote:
> Actually I don't think this number is honored at all. When I set max
> connections to 10 I see like 68 open file descriptors in one of my tests
On 06/27/2011 12:30 PM, Marco Peereboom wrote:
> Would merging these patches help?
> https://bugs.webkit.org/show_bug.cgi?id=35721
> https://bugs.webkit.org/show_bug.cgi?id=35573
I was talking about HTTP connections. I have no idea how WebSockets
connections are managed. (That happens inside WebKi
On Mon, Jun 27, 2011 at 12:46:31PM -0400, David Hill wrote:
> On Mon, Jun 27, 2011 at 12:19:08PM -0400, Dan Winship wrote:
> :On 06/24/2011 04:49 PM, David Hill wrote:
> :> When using a browser with WebkitGTk 1.4.1, I get a lot of CLOSE_WAITs
> :> sitting around. Does Webkit open up sockets itself
On Mon, Jun 27, 2011 at 12:19:08PM -0400, Dan Winship wrote:
:On 06/24/2011 04:49 PM, David Hill wrote:
:> When using a browser with WebkitGTk 1.4.1, I get a lot of CLOSE_WAITs
:> sitting around. Does Webkit open up sockets itself, or does it solely
:> use libsoup to do the web connections?
:
:Thi
On Mon, Jun 27, 2011 at 12:19:08PM -0400, Dan Winship wrote:
> On 06/24/2011 04:49 PM, David Hill wrote:
> > When using a browser with WebkitGTk 1.4.1, I get a lot of CLOSE_WAITs
> > sitting around. Does Webkit open up sockets itself, or does it solely
> > use libsoup to do the web connections?
>
On 06/24/2011 04:49 PM, David Hill wrote:
> When using a browser with WebkitGTk 1.4.1, I get a lot of CLOSE_WAITs
> sitting around. Does Webkit open up sockets itself, or does it solely
> use libsoup to do the web connections?
This is one of the leftover bits of historical lameness in libsoup. It
On Fri, Jun 24, 2011 at 02:26:48PM -0700, Martin Robinson wrote:
:On Fri, Jun 24, 2011 at 1:49 PM, David Hill wrote:
:> When using a browser with WebkitGTk 1.4.1, I get a lot of CLOSE_WAITs
:> sitting around. Does Webkit open up sockets itself, or does it solely
:> use libsoup to do the web conne
On Fri, Jun 24, 2011 at 02:26:48PM -0700, Martin Robinson wrote:
> On Fri, Jun 24, 2011 at 1:49 PM, David Hill wrote:
> > When using a browser with WebkitGTk 1.4.1, I get a lot of CLOSE_WAITs
> > sitting around. Does Webkit open up sockets itself, or does it solely
> > use libsoup to do the web c
On Fri, Jun 24, 2011 at 1:49 PM, David Hill wrote:
> When using a browser with WebkitGTk 1.4.1, I get a lot of CLOSE_WAITs
> sitting around. Does Webkit open up sockets itself, or does it solely
> use libsoup to do the web connections?
> Has anyone else experienced this?
> I am wondering if there
When using a browser with WebkitGTk 1.4.1, I get a lot of CLOSE_WAITs
sitting around. Does Webkit open up sockets itself, or does it solely
use libsoup to do the web connections?
Has anyone else experienced this?
I am wondering if there is a missing close() somewhere...
- David
19 matches
Mail list logo
