Nikita,
Please do not post duplicate threads
That said, your issue smells a little like this issue posted on StackOverflow. You could try lowering your heap size but better yet, make sure you’re running a 64 bit JVM. I would suspect something changed on your build machines with regard to the Java installation.
A reminder that anything set in sonar.propeties (as you mentioned in your other thread) is only relevant on the server-side, not the scanning side. Setting JVM options for the Scanner is done as documented here.
(Note: the latest version of the SonarQube Scanner for MSBuild is 4.3.1)
Colin