Edgewall Software

Changes between Version 21 and Version 22 of TracSubversion


Ignore:
Timestamp:
Aug 29, 2006, 8:51:18 PM (18 years ago)
Author:
Christian Boos
Comment:

More details about #2611 and point to the workaround explained in #3455

Legend:

Unmodified
Added
Removed
Modified

  • TracSubversion

    v21 v22  
    8383However, some people are seeing yet another problem, which requires
    8484one more fix:
    85  * Issue #2611 (intermittent fatal error) [[BR]]
    86    which was supposedly fixed by applying this
     85 * Issue #2611 (intermittent fatal error, manifesting itself with `"argument number 0: a 'apr_pool_t *' is expected"` messages in the log and segfault of the apache server) [[BR]]
     86   was supposedly fixed by applying this
    8787   [attachment:ticket:2611:application_pool_race_condition_fix.txt patch] to
    8888   `subversion/bindings/swig/include/proxy_apr.swg`.
    89    Note that this requires to regenerate the SWIG bindings,
    90    as explained in [/trac/ticket/2611#change_21 here].
     89   Note that after applying this patch, the SWIG bindings would have to be regenerated,
     90   as explained [comment:ticket:2611:16 here].
    9191   It should be emphasized that a compatible version of SWIG
    9292   must be used (`1.3.24`, `1.3.25`). [[BR]]
    93    Should be fixed in Subversion 1.3.1 (as the above patch was integrated as !r18721)
     93   The issue was supposed to be fixed in Subversion 1.3.1, as the above patch was integrated as !r18721, but actually the patch was not enough to solve the issue. See below.
    9494
    9595==== Trac and Subversion 1.3.1 ====
    9696
    9797As mentioned above, the issues found with 1.3.0 should be fixed
    98 by 1.3.1.
    99 However, I've not ''yet'' tried 1.3.1. so I can't tell for sure
    100 that there won't be any issues...
     98by 1.3.1. This is mostly true, except for #2611.
    10199
    102 Note:
    103100'''Issue #2611 was confirmed to still exists in Subversion 1.3.1''' and also in the stock 1.3.2,
    104101when compiled using the pre-generated bindings that were produced using SWIG 1.3.25[[br]]
    105102So it seems the patch discussed above was not enough to solve the problem.
    106 Also, ''the issue is most certainly related to the use of multiple python sub-interpreters'', either because those are created by default when different virtual hosts are used (#2965, #3455) or because different `"PythonInterpreter"` directives are used in different <Location> sections (#2713).
     103Also, ''the issue is most certainly related to the use of multiple python sub-interpreters'', either because those are created by default when different virtual hosts are used (#2965, #3455) or because different `"PythonInterpreter"` directives are used in different <Location> sections (#2713). A workaround consists of forcing the use of a single Python interpreter, using the `"PythonInterpreter"` directive with the same argument for all the virtual hosts, as explained [comment:ticket:3455:5 here].
    107104
    108105==== Trac and Subversion 1.3.2 ====
    109106
    110 This version adds support for SWIG 1.3.28.
     107This version adds support for SWIG 1.3.28. It remains to be seen if a binding built with wrappers generated by 1.3.28 are enough to fix #2611, but I'm skeptical at this point.
    111108
    112109See also: [http://svn.collab.net/repos/svn/tags/1.3.2/CHANGES release notes for 1.3.2]
    … …  
    121118Also, that version supports SWIG 1.3.29, but so far I used the 1.3.25 pre-generated wrappers that are bundled with the tarball.
    122119
     120Same remark as above concerning #2611, if I have some time, I'll try to reproduce the issue.
     121
    123122See also: [http://svn.collab.net/repos/svn/tags/1.4.0-rc5/CHANGES release notes for 1.4.0]
    124123