On Thu, Jun 11, 2009 at 10:24 PM, Stuart
Morganstuartmor...@chromium.org wrote:
Also, 256 is a pretty low limit.
Dialing it up a few notches (say to 1024) to improve the performance
of a better overall solution certainly isn't an issue.
Don't you need root for that?
- Dan
On Fri, Jun 12, 2009 at 6:59 AM, Dan Kegeldaniel.r.ke...@gmail.com wrote:
Don't you need root for that?
Changing the soft limit doesn't require root, and there's apparently
no hard limit at all on file descriptors (at least as of Leopard; I
don't think that was always true).
-Stuart
In my experience, taking code which assumes a low number of file
descriptors and just ramping up the file descriptor limits to
accommodate a particular case doesn't work out well. You end up
finding out that there are three or four other edge cases which cause
problems, things like O(N^2) code
On Thu, Jun 11, 2009 at 5:13 PM, Stuart Morganstuartmor...@chromium.org wrote:
I'm working on getting the Intl2 test set from the page cycler up and
running on the Mac, which currently crashes very quickly. It turns out
that one of the test pages has hundreds of images on it, and we
On Thu, Jun 11, 2009 at 5:13 PM, Stuart Morgan stuartmor...@chromium.orgwrote:
I'm working on getting the Intl2 test set from the page cycler up and
running on the Mac, which currently crashes very quickly. It turns out
that one of the test pages has hundreds of images on it, and we
On Thu, Jun 11, 2009 at 7:45 PM, Darin Fisher da...@chromium.org wrote:
On Thu, Jun 11, 2009 at 5:13 PM, Stuart Morgan
stuartmor...@chromium.orgwrote:
I'm working on getting the Intl2 test set from the page cycler up and
running on the Mac, which currently crashes very quickly. It turns
On Thu, Jun 11, 2009 at 7:45 PM, Darin Fisherda...@chromium.org wrote:
It seems like this issue, since it is about the shared memory used for
streaming resources to a renderer, is not particular to file://. It could
happen with http:// as well assuming we had a fast enough network or a janky
On Thu, Jun 11, 2009 at 8:03 PM, Michael Nordmanmicha...@google.com wrote:
Sounds like the underlying issue is not the number of requests (or
type of request), but the number of SharedMemory instances in use on
behalf of request handling at any one time.
True; I'll take a look at how else
