check your network.http.max-persistent-connections-per-server and network.http.max-connections-per-server.
ax
2009-03-25 05:52:25
A:
Thanks but it's not an FF issue.
2009-03-25 06:53:57
A:
Never encountered anything like that. Are you sure you're not using CGI instead of FastCGI? Also check how many php processes your webserver spawns and how many requests they can handle each.
To help with testing you might want to put sleep function in test-page.
Maiku Mori
2009-03-25 06:00:09
A:
I'm seeing the same issue. A processing intensive is triggered by an ajax call before the browser is directed to the next page, but this second page refuses to load until the first taks, which was started asynchronously, is finished.
Did you ever find a fix for this?
Jordan
2010-10-09 04:36:51