Trac crashes Apache with mod_python under Windows 2000
|Reported by:||Owned by:||Jonas Borgström|
I'm running Trac 0.9.4 on Windows 2000 with Apache 2.0.55 with mod_python 3.2.8. About 2 or 3 times per day Apache crashes with the following error (loosely translated from Russian) popping up at the console:
Instruction at address 0x1e05db6f accessed memory at address 0xd8ebc005. Memory cannot be read
Because of this message, Apache service doesn't restart automatically (the process isn't really terminated till I click on Ok button), which is obviously bad.
Until recently, this bug had affected other developers working on our project, but now I've seen it as well. I've just logged in to Trac, clicked on the "Timeline", and Trac output the following in the browser:
Trac detected an internal error: argument to += must be iterable
with Python traceback:
Traceback (most recent call last): File "C:\Python23\lib\site-packages\trac\web\modpython_frontend.py", line 206, in handler dispatch_request(mpr.path_info, mpr, env) File "C:\Python23\lib\site-packages\trac\web\main.py", line 139, in dispatch_request dispatcher.dispatch(req) File "C:\Python23\lib\site-packages\trac\web\main.py", line 107, in dispatch resp = chosen_handler.process_request(req) File "C:\Python23\lib\site-packages\trac\Timeline.py", line 140, in process_request filters) TypeError: argument to += must be iterable
Unfortunately, the logging wasn't turned on at the time, I'll turn it on ASAP and will try to reproduce the error again. I'll add more details if I'll succeed.
Its worth noting that this same Trac site had ran for about a month and a half in CGI mode, without any problems whatsoever, so this is mostlikely either a mod_python or a threading issue.
If I can help to troubleshoot this in any way, just let me know.