I think this must be an issue with either your web server, the network, your workstation or the browsers. I don't see how this is a Mailman bug.
The normal consequence of "too many requests" in the admindb interface is that the process times out before producing any output (it has to go through all the requests and sort them before it can build the page). Once the admindb CGI has built the page and produced its HTML output (which is done all at once with a single 'print' statement), it is done. If the output arrives at your browser in increments and the browser "freezes and thaws", this is between the web server, the network, the browser and the workstation on which the browser is running. It has nothing to do with Mailman until you ultimately click a 'submit' button.
My best guess is you should try a workstation with more RAM.
I think this must be an issue with either your web server, the network, your workstation or the browsers. I don't see how this is a Mailman bug.
The normal consequence of "too many requests" in the admindb interface is that the process times out before producing any output (it has to go through all the requests and sort them before it can build the page). Once the admindb CGI has built the page and produced its HTML output (which is done all at once with a single 'print' statement), it is done. If the output arrives at your browser in increments and the browser "freezes and thaws", this is between the web server, the network, the browser and the workstation on which the browser is running. It has nothing to do with Mailman until you ultimately click a 'submit' button.
My best guess is you should try a workstation with more RAM.