08-31-2012, 10:07 PM
Seems like a regular deadlock, so let's treat it like one.
Download this tool from MS:
http://www.microsoft.com/en-us/download/...px?id=4060
It installs a commandline tool, userdump.exe, that can create memory dumps for processes. Two versions are installed, x86 for 32-bit systems and x64 for 64-bit systems. Use the correct version for your OS.
Then, start the server and replicate the problem.
Use Task Manager to find the Process ID (PID) of the server.
Start a new commandline window, navigate to the userdump tool and run "userdump <pid>", for example "userdump 232". This will create a file, "MCServer.dmp", in the current folder. Pack the file (it will be rather large, but should compress well) and post it somewhere for me to download.
Note that this file is only useful if you use a nightbuild from the nightbuild page; if you build your own executable, you need to provide me with the exe and all the pdb files, too.
Download this tool from MS:
http://www.microsoft.com/en-us/download/...px?id=4060
It installs a commandline tool, userdump.exe, that can create memory dumps for processes. Two versions are installed, x86 for 32-bit systems and x64 for 64-bit systems. Use the correct version for your OS.
Then, start the server and replicate the problem.
Use Task Manager to find the Process ID (PID) of the server.
Start a new commandline window, navigate to the userdump tool and run "userdump <pid>", for example "userdump 232". This will create a file, "MCServer.dmp", in the current folder. Pack the file (it will be rather large, but should compress well) and post it somewhere for me to download.
Note that this file is only useful if you use a nightbuild from the nightbuild page; if you build your own executable, you need to provide me with the exe and all the pdb files, too.