Jan. 19, 2014
12:17 a.m.
Hi Jonathan, On Jan 17, 2014, at 6:22 PM, Jonathan Vanasco <twisted-python@2xlp.com> wrote:
the following is a rough composite of what is going on. if anyone sees an obvious fix, i'd be greatly appreciative.
I'd love to help, but a "rough composite" is hard to make guesses about, especially since you're talking about hard-to-predict memory-consumption behavior. Can you attach a <http://sscce.org/> which is actually runnable, for example, with a canned list of input URLs (or better yet with an included web server so the URLs can be localhost and more predictable), so we can debug and diagnose a running program instead of ideas about the outline of one? -glyph