'Send more information' after a crash is trying to use infinite memory

35 views
Skip to first unread message

Mike Schlueter

unread,
Jun 14, 2019, 3:54:27 PM6/14/19
to TortoiseSVN
TortoiseSVN crashed just after completing a commit of a few hundred files. 
The "Do you want to send more information about the problem?" prompt popped up, so I clicked "Send information".  
I gave it several minutes to work, then noticed that my computer was really slow. Task Manager showed TortoiseSVN x64 using close to 25GB of RAM!?!
I killed the TortoiseSVN process, and rebooted. 

I have tried to update, but TortoiseSVN reported that it needed Cleanup. 

I tried Cleanup, and it crashed again. Again, the do you want to send information prompt. Again, several minutes, a multiple GB of RAM usage later, I killed it. 
I have repeated this several times now. 

This is my work computer, Win10 1709. 
I have Version 1.12 installed.

It seems like the information gathering routine is getting stuck in a loop. 

Mike Schlueter

unread,
Jun 14, 2019, 3:57:51 PM6/14/19
to TortoiseSVN
Okay, I just tried it again, and I see in Task manager that it's not the reporting app, but the crashing app that is using infinite memory. 
They showed up separate this time, instead of under the same task.
I killed the crashing process, and the reporting dialog disappeared. Not sure if it reported what it had, or got aborted.

Mike Schlueter

unread,
Jun 14, 2019, 4:02:59 PM6/14/19
to TortoiseSVN
Another experiment. 
If I un-check everything under "Clean up working copy status", it doesn't crash, but it doesn't succeed on cleaning. 
If I do it again with "Break write locks" checked, it crashes. 

Stefan

unread,
Jun 15, 2019, 8:57:44 AM6/15/19
to TortoiseSVN


On Friday, June 14, 2019 at 10:02:59 PM UTC+2, Mike Schlueter wrote:
Another experiment. 
If I un-check everything under "Clean up working copy status", it doesn't crash, but it doesn't succeed on cleaning. 
If I do it again with "Break write locks" checked, it crashes. 

this indicates that your working copy got somehow corrupted.
I think you need to do a fresh checkout, sorry.


Reply all
Reply to author
Forward
0 new messages