On Thu, Jun 11, 2009 at 7:45 PM, Darin Fisher<[email protected]> 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 > enough local system, right?
I was assuming that in most cases the max-connections-per-server would tend to prevent us from getting to that point, but it's probably possible given the right circumstances. -Stuart --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
