I'm trying to use the OpsHub migration tool to get our source code onto Visual Studio Online. Partway through the migration, the progress page indicates an error occurred and that the migration has halted, and yet the process still continues to run (ie - Migration Status still says it's Running, and process manager indicates work is still being done by the opshubtfsservice.exe process).
If I click on the hyper link in the error message, it opens a popup dialog indicating there's been a Java heap space error of some kind. Looking closer at running processes, I can see the Java.exe process is using up over 2GB of RAM. I'm running the migration tool on a Windows 7 x64 machine with 16GB of RAM and loads of disc space free. Source server is running TFS 2013.
I've run the tool a few times now, and run into the same issue right at the same point during the migration (xxxx/yyyy Chageset(s)/Label(s) passed). It doesn't seem to get to xxxx+1/yyyy, but perhaps I just need to let it run longer as it's likely chewing on some large changeset of somekind.
Any suggestions on how, or if it's possible to get passed this error? Should I be concerned about it, or just roll with it and see what happens if I let the process continue?
