Also, while Chrome is spinning, I can open Firefox and load pages (including the problem page) just fine. So it's not that the server is overloaded or anything like that...
_Nik On 7/3/2013 5:39 PM, Nikolas Stevenson-Molnar wrote: > I've just updated to Django 1.5 and am running into a problem when > using Chrome with the Django devlopment server (and staticfiles). One > particular page which loads a lot of static content /consistently/ > hangs in Chrome (works fine in Firefox). This seems similar to two > resolved issues: https://code.djangoproject.com/ticket/16099 and > https://code.djangoproject.com/ticket/18336. Except that I've waited > several minutes and the resources haven't finished loading. I've > increased request_queue_size as suggested in the second issue (first > to 10, then 20, then 50) with no change. > > I'd chalk this up entirely as a Chrome problem, except that if I > switch back to Django 1.4 (changing nothing else), everything goes > back to working fine. So what changed about runserver in Django 1.5 > that might cause this? And more importantly, how do I get around it? > I'm running everything on Windows 7 with Django 1.5.1 and the latest > version of Chrome. > > Thanks, > _Nik -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
