By creating thread dumps, you can help us fix program lock-ups (UI freezes, never-ending operations, etc.) and performance problems, among other things. How a thread dump is created depends on your operating system. In the following, we'll assume DeepGit has been installed in the directory
deepgitc.exe) processes in the Windows Task Manager.
bin\deepgitc.exe > dump.txt. This will start DeepGit and keep the command prompt attached to the program.
<install-dir>/DeepGit.app/Contents/MacOS/DeepGit > ~/dump.txt
ps -A | grep DeepGitto find the process ID (PID) of the running DeepGit instance.
kill -3 PIDwhere PID is the process ID you obtained in the previous step. This will append a thread dump to
~/dump.txt. Then wait a few seconds and repeat this step at least 5 times in order to get a reasonable number of dumps.
javaprocess, and you can enter
ps -A | grep javain the terminal to find all running
javaprocesses. If you have other Java applications running, you may execute
ps -Af | grep javato find out the process IDs (PID) of the DeepGit processes. Terminate all of these processes, if there are any.
<install-dir>/bin/deepgit.sh > dump.txt.
ps -a | grep javato find out the process ID of DeepGit's
javaprocess. If there's more than one, you'll have to try them all.
kill -3 PIDin the second terminal window, where PID is the process ID you obtained in the previous step. Wait a few seconds and create a another dump. Repeat this step at least 5 times. After you're done, make sure the file
dump.txthas actually been filled.
How to send the dump.txt file: Compress the
dump.txt file as a zip or tar/gzip archive, and also include the file
log.txt from DeepGit's settings directory. Send this archive, as well as a short description of how to reproduce the problem, to [email protected].