Hi,
>> But from what you've mentioned above, I think it's not the drdump handler that gets invoked but the windows crash handler - which indicates a crash in a third-party dll. <<OK, that makes sense since the dump dialog didn't have the drdump watermark on the dialog.
>> you could have windows collect the crash dumps, put them online somewhere and send me the link so I can try and debug the problem <<
I've uploaded a few crash dumps to Google Drive at https://drive.google.com/open?id=0B1hRnHGpntEXbWJUOFdMOXFWVXM. They are from different causes. One is the Commit dialog (as previously described) and the others are from the Show Log dialog, when trying to edit the commit message. Having managed to a little digging of my own, I can see that they all report exception code 0x00000374 which seems to be heap corruption.
Since the earlier report, I tried to narrow down the Windows Update that might have been the issue. However, it proved to be less successful installing and restoring than I had hoped. Having repeated the cycle a few times, I found that the problem was evident even after restores to times that I had thought were good. I now wonder if the problem has been there longer than I thought but intermittent. Anyway, since restoring to before the Windows Updates were applied wasn't fixing it, I decided to apply all the outstanding Windows Updates, since there was an outside chance that something might have been fixed by the updates. Unfortunately, the problems continue. Currently, I'm finding that I'm mostly working with the SVN command line now and very much miss TortoiseSVN.
Thanks,Bruce
On Tuesday, 17 January 2017, 19:51, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
On 11.01.2017 11:55, bjc_tsvn_at_btinternet.com wrote:
[snip]
> I note from the TortoiseSVN crash handler page
> (https://tortoisesvn.net/crashhandler.html) that TortoiseSVN seems to
> use drdump.com. Have the errors described above been dumped to
> drdump.com? If so, how do I find and review the relevent dumps?
if the drdump crash handler is invoked and you send the report, the
browser is automatically opened to the drdump page of your crash dump.
But from what you've mentioned above, I think it's not the drdump
handler that gets invoked but the windows crash handler - which
indicates a crash in a third-party dll.
>
> I understand that the problem may not be with TortoiseSVN directly. Is
> there any information I can get from TortoiseSVN to help identify the
> underlying issue?
you could have windows collect the crash dumps, put them online
somewhere and send me the link so I can try and debug the problem:
https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3201890
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3203156
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-01-21 02:38:24 CET