Guest User

New issue

a guest
Dec 3rd, 2017
157
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.73 KB | None | 0 0
  1. c:\Users\Zachary Leask\Desktop\Mod>gradlew setupDecompWorkplace
  2. To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/2.14/userguide/gradle_daemon.html.
  3.  
  4. FAILURE: Build failed with an exception.
  5.  
  6. * What went wrong:
  7. Unable to start the daemon process.
  8. This problem might be caused by incorrect configuration of the daemon.
  9. For example, an unrecognized jvm option is used.
  10. Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14/userguide/gradle_daemon.html
  11. Please read the following process output to find out more:
  12. -----------------------
  13. Error occurred during initialization of VM
  14. Could not reserve enough space for 3145728KB object heap
  15.  
  16.  
  17. * Try:
  18. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
  19.  
  20. c:\Users\Zachary Leask\Desktop\Mod>gradlew setupDecompWorkplace --stackrace
  21. To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/2.14/userguide/gradle_daemon.html.
  22.  
  23. FAILURE: Build failed with an exception.
  24.  
  25. * What went wrong:
  26. Unable to start the daemon process.
  27. This problem might be caused by incorrect configuration of the daemon.
  28. For example, an unrecognized jvm option is used.
  29. Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14/userguide/gradle_daemon.html
  30. Please read the following process output to find out more:
  31. -----------------------
  32. Error occurred during initialization of VM
  33. Could not reserve enough space for 3145728KB object heap
  34.  
  35.  
  36. * Try:
  37. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Advertisement
Add Comment
Please, Sign In to add comment