You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by David James <dj...@collab.net> on 2006/01/29 06:49:46 UTC
Re: SWIG Python - memory growing out of bounds
On 20 Jan 2006 12:34:41 +0100, Lars Gullik Bjønnes <la...@gullik.net> wrote:
> | On Fri, 2006-01-20 at 02:25 +0100, Lars Gullik Bjønnes wrote:
> | > Hi,
> | >
> | > I have tried to setup trac for use with subversion (1.3.0). So far
> | > with little success. During the initialization of the database, it
> | > crashes due to excessive use of memory. I have used som time on this
> | > and have tracked this problem down to a problem with the pools and
> | > svn_swig_py_make_editor. I have now reached the point where I am
> | > unable to make further progress.
> | >
> | > Please have a look at the trac ticket I entered:
> | > http://projects.edgewall.com/trac/ticket/2620
> | >
> | > If I can get some directions on how to proceed and what to test now
> | > I'd be happy.
>
> That is where I am comming from (or the ticket system really) ... as
> said: "problem with the pools and svn_swig_py_make_editor", which is
> from the libsvn python bindings.
Hi Lars,
Thanks for your bug report! This bug has been fixed in Subversion
trunk and the fix should be included with 1.3.1. If you would like to
fix your local copy, please see the patch included in the Trac issue:
http://projects.edgewall.com/trac/ticket/2620
Sorry for the delayed response! In future, please send bug reports to
<de...@subversion.tigris.org>. If the bug is regarding the Python
bindings you can cc me to bring it to my attention.
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Loosen guidelines/language for the issue tracker
Posted by kf...@collab.net.
Daniel Rall <dl...@collab.net> writes:
> Max and I were discussing the other side of this coin the other day on
> IRC. He was saying that there were previously a lot more bug reports
> (around 1.0 the timeframe?), which initially spurred instigation of
> the tight issue tracker guidelines. If bug reports have slowed up a
> bit, perhaps the language on the tracker page should be changed to be
> more allowing of obvious reports going straight into the tracker?
>
> In any case, I'm +1 on David's suggestion.
Done, r18304 and r18305 (sorry for the two revisions, just a slip o'
the keyboard).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Loosen guidelines/language for the issue tracker
Posted by Daniel Rall <dl...@collab.net>.
On Sun, 29 Jan 2006, David James wrote:
...
> > Perhaps the language on
> > http://subversion.tigris.org/project_issues.html "Issue tracker guidelines" should be
> > relaxed a bit?
> >
> > After beeing chastised a bit ealier, I was reluctant on approaching
> > the dev list directly.
>
> A safe rule is: If you are trying to help Subversion development, send
> your mail to dev@. For this reason, bug reports are always welcome on
> the dev@ list, especially if the bug report contains all the
> information we need to reproduce the bug on our own systems.
>
> We should probably update project_issues.html and bugs.html to note
> that detailed bug reports are welcome on the dev@ list. I am often
> disappointed to miss important bug reports because they were only sent
> to the users@ list, which I do not read as often.
Max and I were discussing the other side of this coin the other day on
IRC. He was saying that there were previously a lot more bug reports
(around 1.0 the timeframe?), which initially spurred instigation of
the tight issue tracker guidelines. If bug reports have slowed up a
bit, perhaps the language on the tracker page should be changed to be
more allowing of obvious reports going straight into the tracker?
In any case, I'm +1 on David's suggestion.
--
Daniel Rall
Re: SWIG Python - memory growing out of bounds
Posted by David James <dj...@collab.net>.
On 29 Jan 2006 14:00:02 +0100, Lars Gullik Bjønnes <la...@gullik.net> wrote:
> | Thanks for your bug report! This bug has been fixed in Subversion
> | trunk and the fix should be included with 1.3.1. If you would like to
> | fix your local copy, please see the patch included in the Trac issue:
> | http://projects.edgewall.com/trac/ticket/2620
>
> Thanks a lot for that. I had already seen your earlier response on
> this list and also on the trac ticket.
>
> Just to be clear: Is it correct that to test the fix I do not have to
> change anything on the server side (svnserve), it is only on the
> client side the fix has to be applied? (I cannot really make changes
> to the server installation at this time)
This fix is client side only. (The server does not need to be
updated.) Let me know whether it helps!
> | Sorry for the delayed response! In future, please send bug reports to
> | <de...@subversion.tigris.org>. If the bug is regarding the Python
> | bindings you can cc me to bring it to my attention.
>
> I'll do that.
>
> Perhaps the language on
> http://subversion.tigris.org/project_issues.html "Issue tracker guidelines" should be
> relaxed a bit?
>
> After beeing chastised a bit ealier, I was reluctant on approaching
> the dev list directly.
A safe rule is: If you are trying to help Subversion development, send
your mail to dev@. For this reason, bug reports are always welcome on
the dev@ list, especially if the bug report contains all the
information we need to reproduce the bug on our own systems.
We should probably update project_issues.html and bugs.html to note
that detailed bug reports are welcome on the dev@ list. I am often
disappointed to miss important bug reports because they were only sent
to the users@ list, which I do not read as often.
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: SWIG Python - memory growing out of bounds
Posted by David James <dj...@collab.net>.
On 29 Jan 2006 14:00:02 +0100, Lars Gullik Bjønnes <la...@gullik.net> wrote:
> | Thanks for your bug report! This bug has been fixed in Subversion
> | trunk and the fix should be included with 1.3.1. If you would like to
> | fix your local copy, please see the patch included in the Trac issue:
> | http://projects.edgewall.com/trac/ticket/2620
>
> Thanks a lot for that. I had already seen your earlier response on
> this list and also on the trac ticket.
>
> Just to be clear: Is it correct that to test the fix I do not have to
> change anything on the server side (svnserve), it is only on the
> client side the fix has to be applied? (I cannot really make changes
> to the server installation at this time)
This fix is client side only. (The server does not need to be
updated.) Let me know whether it helps!
> | Sorry for the delayed response! In future, please send bug reports to
> | <de...@subversion.tigris.org>. If the bug is regarding the Python
> | bindings you can cc me to bring it to my attention.
>
> I'll do that.
>
> Perhaps the language on
> http://subversion.tigris.org/project_issues.html "Issue tracker guidelines" should be
> relaxed a bit?
>
> After beeing chastised a bit ealier, I was reluctant on approaching
> the dev list directly.
A safe rule is: If you are trying to help Subversion development, send
your mail to dev@. For this reason, bug reports are always welcome on
the dev@ list, especially if the bug report contains all the
information we need to reproduce the bug on our own systems.
We should probably update project_issues.html and bugs.html to note
that detailed bug reports are welcome on the dev@ list. I am often
disappointed to miss important bug reports because they were only sent
to the users@ list, which I do not read as often.
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SWIG Python - memory growing out of bounds
Posted by Lars Gullik Bjønnes <la...@gullik.net>.
David James <dj...@collab.net> writes:
| On 20 Jan 2006 12:34:41 +0100, Lars Gullik Bjønnes <la...@gullik.net> wrote:
| > | On Fri, 2006-01-20 at 02:25 +0100, Lars Gullik Bjønnes wrote:
| > | > Hi,
| > | >
| > | > I have tried to setup trac for use with subversion (1.3.0). So far
| > | > with little success. During the initialization of the database, it
| > | > crashes due to excessive use of memory. I have used som time on this
| > | > and have tracked this problem down to a problem with the pools and
| > | > svn_swig_py_make_editor. I have now reached the point where I am
| > | > unable to make further progress.
| > | >
| > | > Please have a look at the trac ticket I entered:
| > | > http://projects.edgewall.com/trac/ticket/2620
| > | >
| > | > If I can get some directions on how to proceed and what to test now
| > | > I'd be happy.
| >
| > That is where I am comming from (or the ticket system really) ... as
| > said: "problem with the pools and svn_swig_py_make_editor", which is
| > from the libsvn python bindings.
|
| Hi Lars,
|
| Thanks for your bug report! This bug has been fixed in Subversion
| trunk and the fix should be included with 1.3.1. If you would like to
| fix your local copy, please see the patch included in the Trac issue:
| http://projects.edgewall.com/trac/ticket/2620
Thanks a lot for that. I had already seen your earlier response on
this list and also on the trac ticket.
Just to be clear: Is it correct that to test the fix I do not have to
change anything on the server side (svnserve), it is only on the
client side the fix has to be applied? (I cannot really make changes
to the server installation at this time)
| Sorry for the delayed response! In future, please send bug reports to
| <de...@subversion.tigris.org>. If the bug is regarding the Python
| bindings you can cc me to bring it to my attention.
I'll do that.
Perhaps the language on
http://subversion.tigris.org/project_issues.html "Issue tracker guidelines" should be relaxed a bit?
After beeing chastised a bit ealier, I was reluctant on approaching
the dev list directly.
--
Lgb
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org