[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TSVNCache x64: Crash report sent although I chose not to send it (or I wasn't even asked)

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sat, 10 Nov 2012 20:31:01 +0100

On 10.11.2012 18:46, Nils Beckmann wrote:
> Hi,
> TSVnCache crashes sometimes for me for a while now (I can't remember
> when it started, maybe after 1.7.10). One way to reproduce seems to be
> to export my Bookmarks from SWare Iron (a Google Chrome-Fork; will test
> with Chrome too). When I enter the filename textbox in the save file
> dialog. I think it happened at other occasions too, often several times
> in a row.
> I run Windows 8 Entperprise x64.
> I then get most of the time this Dialog.
> ---------------------------
> TSVNCache x64
> ---------------------------
> This problem occurs first time and TortoiseSVN really need this report
> to fix the problem in a future version of TSVNCache x64.
> Are you sure you don't want to send it?
> ---------------------------
> Ja Nein
> ---------------------------
> When I choose Ja (meaning yes), neverless a crash report is send to
> crash-server.com. For instance (actually it seems to be same problem
> number every time, at least for the last occurences):
> ---------------------------
> Report information
> Manufacturer TortoiseSVN
> Application name TortoiseSVN
> Application version
> Problem state New
> Problem 6809
> Dump group 17743
> Dump 182838
> ---------------------------
> It also happened that the report was send without me being asked. This
> one for example:
> ---------------------------
> Manufacturer TortoiseSVN
> Application name TortoiseSVN
> Application version
> Problem state New
> Problem 7474
> Dump group 19372
> Dump 182842
> ---------------------------

First of all, there are no crash reports sent if you don't want to. All
that is sent to the server after a crash is part of the crash stack
trace to find out if the problem has been reported before (kind of a
crash id). No (and I mean absolutely no) personal data is sent there.

Only if you click "yes" to send the report, we get a crash dump which
can contain some personal information (e.g., urls of your repository,
file paths of your working copy, ...).

That said:
I've analyzed your crash reports.
The crash happens in a thread the OS kernel creates in processes. It's
not a thread that TSVNCache creates itself.
I'm not sure why it crashes. All I could find out is that either you
have a very unstable network or part of your hardware is soon to give up
completely (it's faulty right now).

More details in case you're interested:
There's a device (could be your harddrive, a network drive, media server
on the network or some other device) that is listed as attached, but
when queried by that OS thread it returns invalid data in the
TP_CALLBACK_INSTANCE struct (that's an driver struct). Because of that
invalid data, the RPC COM object tries to access invalid data and the
crash happens.

In the whole stack trace of your sent crash dump, no code in TSVNCache
is involved at all.

Since you've mentioned that these crashes started to happen a while ago
but didn't before, I suggest you run a hardware diagnostic tool on your
machine to find out exactly which part of your hardware is at fault here
and replace it immediately.

Of course, it could be just faulty RAM: if the RAM is faulty, anything
can happen and it can even appear that other hardware is defect even
though it's not.

Sorry that I can't tell you exactly why it crashes.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-10 20:31:13 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.