You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Stefan Kueng <to...@gmail.com> on 2014/05/27 20:23:54 UTC
crash reports
Hi,
There are several crash reports sent for TortoiseSVN that I can't figure
out. I've analyzed multiple dumps from those reports but I'm not
successful in finding the root cause.
I *think* it's because the crashes happen due to wrong pool handling,
i.e. pools are destroyed but then used again, and that makes it
impossible (for me at least) to find the problem.
Maybe one of you guys can analyze the crash dumps and find out what's
going on here?
https://www.crash-server.com/AppVersion.aspx?ClientID=tsvn&AppVersionID=364
this crash is really happening a lot (3594 dumps as of now, and it's
only been three weeks since the last release):
https://www.crash-server.com/Problem.aspx?ClientID=tsvn&ProblemID=72258
the second one has 1672 dumps already and it seems to be the same root
cause:
https://www.crash-server.com/Problem.aspx?ClientID=tsvn&ProblemID=71413
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
Re: crash reports
Posted by Stefan Kueng <to...@gmail.com>.
On 28.05.2014 12:28, Bert Huijben wrote:
>
>
>> -----Original Message-----
>> From: Stefan Kueng [mailto:tortoisesvn@gmail.com]
>> Sent: dinsdag 27 mei 2014 20:24
>> To: 'Subversion Development'
>> Subject: crash reports
>>
>> Hi,
>>
>> There are several crash reports sent for TortoiseSVN that I can't figure
>> out. I've analyzed multiple dumps from those reports but I'm not
>> successful in finding the root cause.
>
> I think some of these crashes are caused by serf 1.3.5... In particular the
> issue fixed in r2360, r2361.
> (Introduced in 1.3.x in r2344)
>
> Lieven doesn't want to backport the fix directly. See [1]
>
> I can reproduce a crash by running
> $ svn co https://svn0.us-west.freebsd.org/base/releng/8.4/contrib crash1 -q
>
> (Will take quite some time to reproduce depending on the internet connection
> you use, but the testcase is pretty stable)
>
>
> Bert
>
> [1] https://groups.google.com/forum/#!topic/serf-dev/3_HLwF2lVsY
Thanks for the info.
I'll add a comment to the crash reports.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
RE: crash reports
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Stefan Kueng [mailto:tortoisesvn@gmail.com]
> Sent: dinsdag 27 mei 2014 20:24
> To: 'Subversion Development'
> Subject: crash reports
>
> Hi,
>
> There are several crash reports sent for TortoiseSVN that I can't figure
> out. I've analyzed multiple dumps from those reports but I'm not
> successful in finding the root cause.
I think some of these crashes are caused by serf 1.3.5... In particular the
issue fixed in r2360, r2361.
(Introduced in 1.3.x in r2344)
Lieven doesn't want to backport the fix directly. See [1]
I can reproduce a crash by running
$ svn co https://svn0.us-west.freebsd.org/base/releng/8.4/contrib crash1 -q
(Will take quite some time to reproduce depending on the internet connection
you use, but the testcase is pretty stable)
Bert
[1] https://groups.google.com/forum/#!topic/serf-dev/3_HLwF2lVsY
Re: crash reports
Posted by Stefan Kueng <to...@gmail.com>.
On 27.05.2014 20:56, Branko Čibej wrote:
> On 27.05.2014 20:23, Stefan Kueng wrote:
>> Hi,
>>
>> There are several crash reports sent for TortoiseSVN that I can't
>> figure out. I've analyzed multiple dumps from those reports but I'm
>> not successful in finding the root cause.
>> I *think* it's because the crashes happen due to wrong pool handling,
>> i.e. pools are destroyed but then used again, and that makes it
>> impossible (for me at least) to find the problem.
>>
>> Maybe one of you guys can analyze the crash dumps and find out what's
>> going on here?
>>
>> https://www.crash-server.com/AppVersion.aspx?ClientID=tsvn&AppVersionID=364
>>
>
> Can you put these somewhere that doesn't require a login? E.g., send a
> text summary to the PMC list? (FWIW, even with the required login,
> you're making the crash dumps public ... hardly good security?)
You can only download the dumps with the login. So the dumps which can
contain private data are *not* public.
A stack trace hardly contains private data, and only those are visible
publicly.
I've sent the login info so you can get the dumps to the private list
before, but I can send them to you privately.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
Re: crash reports
Posted by Branko Čibej <br...@wandisco.com>.
On 27.05.2014 20:23, Stefan Kueng wrote:
> Hi,
>
> There are several crash reports sent for TortoiseSVN that I can't
> figure out. I've analyzed multiple dumps from those reports but I'm
> not successful in finding the root cause.
> I *think* it's because the crashes happen due to wrong pool handling,
> i.e. pools are destroyed but then used again, and that makes it
> impossible (for me at least) to find the problem.
>
> Maybe one of you guys can analyze the crash dumps and find out what's
> going on here?
>
> https://www.crash-server.com/AppVersion.aspx?ClientID=tsvn&AppVersionID=364
>
Can you put these somewhere that doesn't require a login? E.g., send a
text summary to the PMC list? (FWIW, even with the required login,
you're making the crash dumps public ... hardly good security?)
-- Brane
--
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com