## Miscellaneous Options |

| On this tab of the profiling settings dialog, you can adjust uncategorized options for profiling.

| The following options are available: VM life cycle control If you select the `Keep VM alive` check box, JProfiler keeps the VM alive until the JProfiler GUI disconnects. This option allows you to profile code sections which are close to a forced termination of the virtual machine. Note: with the classic VM (e.g. IBM JVMs), this option installs a security manager which intercepts your application's calls to `System.exit()` and executes them after JProfiler's GUI front end disconnects. This can be a problem when you profile an application server which installs its own security manager. If you use a classic VM and get security related exceptions when profiling your applications, try unchecking this option. Dynamic views Many views in JProfiler update their data automatically. There are several options for configuring the update behavior of those dynamic views: Start with all views frozen To disable dynamic updates in JProfiler's views, you can check Start with all dynamic views frozen. Click on the unfreeze button in the toolbar if you want to start dynamic data to be displayed or fetch data manually with the fetch data button which is visible only in the frozen state. Transmission periods Based on the varying degree of computing expenses required for the different views, the transmission periods for the dynamic views have been split into two separate settings: CPU views This setting influences the update interval of the dynamic views in the CPU view section. Tables and graphs This setting influences the update interval of the all objects view recorded objects view dynamic views in the thread section VM telemetry view section Note: The update frequency of the all objects view is adjusted automatically according to the total number of objects on the heap. To update any dynamic view in between two regular updates, you can click on the refresh icon in the status bar. Console Settings JProfiler displays a console for locally started programs. This includes local sessions, applets, web start applications and remote sessions with a configured start command. JProfiler offers two types of consoles: Java Console This is a cross-platform console, that supports text input, sending CTRL-C to the profiled application, text selection and clipboard operations. For the Java console you can set the following options: Buffer size The number of most recent lines of output that are held by the console. Default is 1000. Window size The initial size (width x height) of the console in characters. Note that the console does not wrap text. Default is 80 x 25. This console integrates with JProfiler's Window menu. Native Console On Microsoft Windows, you also have the option to use the native console. This console does not integrate with JProfiler's Window menu. Profiling agent debug parameters Here you can enter debugging parameters that can be passed to the profiling agent on the command line. This text box is not visible for remote sessions, since you have to add those parameters to the start script yourself in that case.