[Trac-tickets] Re: [The Trac Project] #1401: crash in svn bindings while browsing the timeline

The Trac Project noreply at edgewall.com
Tue Apr 5 05:44:33 EDT 2005


#1401: crash in svn bindings while browsing the timeline
---------------------+------------------------------------------------------
       Id:  1401     |      Status:  new                     
Component:  general  |    Modified:  Tue Apr  5 05:44:29 2005
 Severity:  normal   |   Milestone:                          
 Priority:  normal   |     Version:  devel                   
    Owner:  jonas    |    Reporter:  cboos                   
---------------------+------------------------------------------------------
Comment (by cboos):

 I surrounded the svn code in the Timeline by a try/except block, but this
 gave nothing.

 But, at one point, I got this:
 {{{
 Unhandled exception in thread started by
 Traceback (most recent call last):
   File "D:\COM\activestace\python-2.3.2-232\lib\threading.py", line 392,
 in __repr__
     assert self.__initialized, "Thread.__init__() was not called"
 AssertionError: Thread.__init__() was not called
 }}}

 There must be a thread problem somewhere.
 If I refresh the timeline very quickly, the crash happens
 at the second or third refresh.
 If I wait enough time (for instance, after the refresh
 progress bar disappears) the crash doesn't happen.

 Indeed, after the crash I see several python threads in the debugger:
 {{{
         2960    Win32 Thread    7c90eb94        Normal  0
 >       3776    Win32 Thread    1e0871e5        Normal  0
         4092    _wrap_apr_pool_destroy  svn_swig_py_acquire_py_lock
 Normal  0
         2264    _wrap_apr_pool_destroy  svn_swig_py_acquire_py_lock
 Normal  0
         312     Win32 Thread    7c90eb94        Normal  0
 }}}

 Detail of the 3776 thread, where the access violation occurs:
 {{{
 >       python23.dll!1e0871e5()
         python23.dll!1e03f2b5()
         python23.dll!1e08372a()
         python23.dll!1e08370c()
 ...
 }}}

 The other python threads are looking like:
 {{{
 >       ntdll.dll!7c90eb94()
         ntdll.dll!7c90e9c0()
         kernel32.dll!7c8025db()
         kernel32.dll!7c8399f3()
         kernel32.dll!7c802542()
         python23.dll!1e080331()
         python23.dll!1e08058b()
         python23.dll!1e012ad8()
         _core.dll!svn_swig_py_acquire_py_lock()  Line 96        C
         _core.dll!_wrap_apr_pool_destroy(_object * self=0x00000000,
 _object * args=0x00c48150)  Line 1480       C
         python23.dll!1e059196()
         python23.dll!1e0169fb()
         python23.dll!1e014b85()
 ...
 }}}

 In order to get a more useful backtrace, I tried to reproduce the problem
 on Linux, but everything seems to be fine there.

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/1401>
The Trac Project <>


More information about the Trac-Tickets mailing list