Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
While I removed the -javaagent argument from the vmoptions file within my Program Files, it persisted in my roaming AppData folder and that seems to be what the IDE was referencing, not the main bi...
Answer
#2: Post edited
While I removed the `-javaagent` argument from the main bin within my Program Files, it persisted in my roaming AppData folder. I believe this [link](https://intellij-support.jetbrains.com/hc/en-us/articles/206544869-Configuring-JVM-options-and-platform-properties) explains what happened:- > Please note that custom .vmoptions file created using 'Edit Custom VM Options' action has the priority over the original file in the bin directory.
- While I removed the `-javaagent` argument from the vmoptions file within my Program Files, it persisted in my roaming AppData folder and that seems to be what the IDE was referencing, not the main bin. I believe this [link](https://intellij-support.jetbrains.com/hc/en-us/articles/206544869-Configuring-JVM-options-and-platform-properties) explains what happened:
- > Please note that custom .vmoptions file created using 'Edit Custom VM Options' action has the priority over the original file in the bin directory.
#1: Initial revision
While I removed the `-javaagent` argument from the main bin within my Program Files, it persisted in my roaming AppData folder. I believe this [link](https://intellij-support.jetbrains.com/hc/en-us/articles/206544869-Configuring-JVM-options-and-platform-properties) explains what happened: > Please note that custom .vmoptions file created using 'Edit Custom VM Options' action has the priority over the original file in the bin directory.