Ticket #7035 (closed defect: duplicate)
Opened 4 years ago
Last modified 3 years ago
Trac Fails to return results on some changesets
| Reported by: | mgorbach@… | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | rendering | Version: | 0.11b2 |
| Severity: | major | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API 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
Change History
comment:1 Changed 4 years ago by anonymous
- Component changed from admin/console to web frontend/mod_python
comment:2 Changed 4 years ago by cboos
- Resolution set to duplicate
- Status changed from new to closed
comment:3 Changed 4 years ago by cboos
- Component changed from web frontend/mod_python to rendering
- Milestone set to 0.11.1
- Resolution duplicate deleted
- Severity changed from normal to major
- Status changed from closed to 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 Changed 3 years ago by cboos
- Milestone 0.11-retriage deleted
- Resolution set to duplicate
- Status changed from reopened to 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.