On Fri, Jun 24, 2011 at 05:06:42PM +0200, Antoine Jacoutot wrote: > On Fri, 24 Jun 2011, Marco Peereboom wrote: > > > I have spent a pretty significant amount of time using webkit 1.4.1 and > > it is a major improvement over 1.4.0 however it still is in a pretty bad > > state. I have started working with the upstream folks to get some > > things resolved however doing anything webkit is painfully slow. > > > > I have run into are crashes, failure to render pages, resource > > starvation etc. > > > > I'd like to suggest we keep a 1.2.x around in addition to 1.4.x for a > > better browsing experience. 1.4.x will eventually get better but right > > now it is painful to use as a daily browser. > > I use it daily without issues. Any particular sites or circumstances > that would help us reproduce the problems you are seeing?
My current best theory is that the brand new link prefetch stuff (ugh!) is easting gobs of file descriptors while another site is loading. So when webkit tries to establish a connection to get like favicon or css it runs out and renders the pages sans css or favicon (missing pictures etc etc). The link prefetch can't be disabled since it doesn't have a knob. I am trying to reason with the webkit people (again) that anything prefetch is not really that great for everybody. In xxxterm the file descriptor starvation has other fun side effects because it opens and closes files left and right for things like state, bookmarks, etc. The easiest way to see this in action is having like 10 tabs created at startup. This usually results in pages not being rendered correctly and xxxterm complaining it can't open files. There is some evidence too that on top of this there is also a fd leak somewhere as well.
