[Trac-tickets] Re: [The Trac Project] #2170: Crash while doing a
login/logout in the Timeline
The Trac Project
noreply at edgewall.com
Mon Oct 10 12:18:48 CDT 2005
#2170: Crash while doing a login/logout in the Timeline
----------------------+-----------------------------------------------------
Reporter: cboos | Owner: cboos
Type: defect | Status: assigned
Priority: highest | Milestone: 0.9
Component: general | Version: devel
Severity: critical | Resolution:
Keywords: |
----------------------+-----------------------------------------------------
Comment (by cboos):
I might have a fix for the issue:
attachment:trac_no_writer_contention.patch
This uses the workaround described in
[http://initd.org/tracker/pysqlite/ticket/126 #py126].
The sqlite binary has to be reconfigured with the
`--enable-threadsafe` flag and recompiled, because
this flag is turned off by default (on Linux) and
the binaries used until now by Trac are most likely
''not'' thread-safe (see #2196).
Therefore, the above patch contains also cmlenz's patch for #2196,
which is a prerequisite for being able to run Trac with a threadsafe
sqlite.
The patches to pysqlite that can be found on #py126
are not absolutely required, but they should help.
Some caveats:
* I haven't tested that on Windows yet
* I've got segfaults due to a second `__del__` call on a Cursor
object (!?). This is happening on SuSE 9.0, with the original python
(`sys.version == "2.3+ (#1, Sep 23 2003, 23:07:16) \n[GCC 3.3.1 (SuSE
Linux)]"`).
This appears to be an early 2.3 release (2.3.1, from the date
information).
* The Python 2.3.4 that I compiled myself seems to be immune to the
problem, so far.
The difference might be due to the changes introduced in Python
[http://www.python.org/2.3.3/NEWS.html#what-s-new-in-python-2-3-3c1
2.3.3c1],
where 2 critical bug fixes involving weakrefs and garbage collection
have been
fixed.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/2170>
The Trac Project <http://trac.edgewall.com/>
More information about the Trac-Tickets
mailing list