Author: SIGSEGV
Subject: [VMMap 3.11] Arguments field in Launch/trace
Posted: 23 February 2014 at 10:35am
Hi,
I'm trying to analyze the memory utilization of some Java application.
Since tracing is only possible when launching the application from inside VMMap, I tried to start it this way.
Problem: The application uses a rather "lenghty" argument string consisting of
- about 200 characters for the %VM_ARGS% provided to the Java VM
- the path to the JAR file to launch
- about 200 characters for the %APP_ARGS% provided to the application itself
- optionally some more switches like -Dtest1 -Dtest2 and so on which could also get about up to more than 100 chars in length
The "Arguments" field in the "Launch/trace a new process" tab seems to be limited to about 256 chars which obviously leads to the argument string being silently cropped :-(
If I restart VMMap I recognize that part of the %APP_ARGS% are missing.
If I just fill in some "crap" exceeding 1000 chars, VMMap64.exe will crash.
Would it be possible to enlarge this internal buffer (e.g. allowing 1024 chars) for the arguments?
Thanks in advance.
Cheers,
SIGSEGV
Subject: [VMMap 3.11] Arguments field in Launch/trace
Posted: 23 February 2014 at 10:35am
Hi,
I'm trying to analyze the memory utilization of some Java application.
Since tracing is only possible when launching the application from inside VMMap, I tried to start it this way.
Problem: The application uses a rather "lenghty" argument string consisting of
- about 200 characters for the %VM_ARGS% provided to the Java VM
- the path to the JAR file to launch
- about 200 characters for the %APP_ARGS% provided to the application itself
- optionally some more switches like -Dtest1 -Dtest2 and so on which could also get about up to more than 100 chars in length
The "Arguments" field in the "Launch/trace a new process" tab seems to be limited to about 256 chars which obviously leads to the argument string being silently cropped :-(
If I restart VMMap I recognize that part of the %APP_ARGS% are missing.
If I just fill in some "crap" exceeding 1000 chars, VMMap64.exe will crash.
Would it be possible to enlarge this internal buffer (e.g. allowing 1024 chars) for the arguments?
Thanks in advance.
Cheers,
SIGSEGV