The traceback is only within the console and from broken pipe.. theres no errors on the page :)
On Mar 5, 10:28 am, Tim Chase <[EMAIL PROTECTED]> wrote: > > To expand on this, sometimes the pages load as they would on our live > > environment, but it randomly (and happens most of the time) hangs to > > where it takes up to a couple minutes to load a page. > > If you disable CSS (or expand all of the collapsed sections of > the traceback), are you getting a mammothly large page? I had > trouble with something like this just recently where the > traceback was pulling in a gargantuan-sized recordset of data > that was supposed to be getting filtered, but that was causing > the traceback. It would look like the server had hung and the > page took ages to load because all 600k records were coming back > and getting built into the traceback dump. > > If you search the archives for my "Preventing tracebacks from > pulling back gobs of data" thread, both Jeremy Dunck and Karen > Tracy gave suggestions for how to prevent this. > > YMMV, > > -tkc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
