Opened 17 years ago
Closed 16 years ago
#7035 closed defect (duplicate)
Trac Fails to return results on some changesets
Reported by: | Owned by: | Christopher Lenz | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | rendering | Version: | 0.11b2 |
Severity: | major | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I have several changesets on my site macfusionapp.org/trac which trac 0.11 beta 2 fails to display at all. It waits a little while and then I get a "page not found" message in Safari. An older version of trac (previous stable) seemed to show these changesets fine, although it took a while. Nothing interesting appears in the log. It stops with a message saying its getting the chrome.
Attachments (0)
Change History (4)
comment:1 by , 17 years ago
Component: | admin/console → web frontend/mod_python |
---|
comment:2 by , 17 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:3 by , 17 years ago
Component: | web frontend/mod_python → rendering |
---|---|
Milestone: | → 0.11.1 |
Resolution: | duplicate |
Severity: | normal → major |
Status: | closed → reopened |
Ok, #7029 had apparently nothing to do with slower changeset rendering, so I'll paste here what I already said on that topic:
A "100% load for about 30-45 second" is unfortunately not uncommon with lengthy pages like big changesets now that they're rendered with Genshi. There are ongoing efforts to speed things up at the Genshi level, including a GSoC proposal.
Please also report the memory usage on server side while Trac is rendering those changesets, as there are known memory issues (#6614) and if the server is swapping, the rendering will be even slower.
comment:4 by , 16 years ago
Milestone: | 0.11-retriage |
---|---|
Resolution: | → duplicate |
Status: | reopened → closed |
See #5170.
If it "took a while" with 0.10-stable, chances are that it now takes "too long" for your Safari browser, which reaches its time out.
See #7029.