ToolsMenuFunctions - Versionsgeschichte

Cg: Weiterleitung nach ToolsMenuFunctions/en erstellt

2016-12-12T17:27:45Z

Weiterleitung nach ToolsMenuFunctions/en erstellt

← Nächstältere Version		Version vom 12. Dezember 2016, 17:27 Uhr
Zeile 1:		Zeile 1:
			#redirect [[ToolsMenuFunctions/en]]
	=== Show all External Connections ===

	Opens an inspector on all external connections which possibly hold a handle to either a socket, pipe or serialPort.

	=== Shut Down Bridge Connections ===

	Tears down leftover JavaBridge connections.

	=== Close all Socket Connections ===

	Tears down leftover socket connections (interprocess communication).

	=== Close all Serial Connections ===

	Tears down leftover serial connections

	=== Show Memory Usage by Object Type ===

	Detailed information about memory usage

	=== Memory Cleanup ===

	Under normal conditions, you don't have to care about expecco's memory: its underlying support system performs automatic memory management (garbage collection). This includes automatic finalization of objects which refer to operating system resources such as file handles, database-connections etc.

	However, these finalizations may happen quite delayed, due to the fact that the garbage collector is usually only invoked when running out of memory or when more memory is requested. This means, that if a file- or database handle has not been closed, but is also no longer used by a testSuite, that handle will be closed (and thereby freed) whenever the next garbage collect operation occurs. Which, if no memory is needed for some time, may happen quite delayed.

	Another situation in which handles are still referenced (and therefore not closed automatically) is when such handles are still present in an activity-log/trace. Because all data which was interchanged between steps is recorded there, handles may end up being recorded and therefore considered to be still "in-use" by the automatic memory management.

	This tool-function forces a garbage collect operation to be triggered immediately, and thereby freeing any unreferenced operating system resources. When those resources get collected, a finalize function is called automatically, which closes the associated operating system handle. Use this, if you have the feeling that the system is using many file, window, socket or other handles.

	Notice: the automatic memory management can of course only free memory which is completely unreachable. This means that objects which are still referenced by other referenced objects will not be reclaimed. In expecco, one such "top level" referrer is usually the result log/execution trace of the previous execution(s).

	This is the storage you see when inspecting pin values after an execution. For example, if a socket or file handle is stored in this execution trace, AND this handle was not properly closed (either because the suite simply forgot to close it, or because the test was aborted and the suite provided no close in its post-action), then the handle might be stored in the log, and is therefore never closed automatically.

	Notice that this behavior is not a bug: it is often very useful, to have external connections still open, when looking at the activity-log,
	because in many contexts you can inspect and interact with the connection if it is still open (remember that objects in remote machines are only references via handles, which are nvalid, if the underlying bridge connection gets closes). This is especially useful in the inspector tool.

	In this case, you should either "''Remove all Results in System''" (in the "''Test-Results''"-menu), and then perform a memory cleanup, or use one of the other maintenance functions from the debugging menu to close handles (i.e. "''Close all Sockets''", "''Close all Bridge Connections''", "''Close all Serial Connections''" etc.).


	Back to [[Online_Documentation#Tools \| Online Documentation]].

Cg: /* Memory Cleanup */

2016-12-12T17:26:39Z

Memory Cleanup

← Nächstältere Version		Version vom 12. Dezember 2016, 17:26 Uhr
Zeile 34:		Zeile 34:

	Notice that this behavior is not a bug: it is often very useful, to have external connections still open, when looking at the activity-log,		Notice that this behavior is not a bug: it is often very useful, to have external connections still open, when looking at the activity-log,
	because in many contexts you can inspect and interact with the connection if it		because in many contexts you can inspect and interact with the connection if it is still open (remember that objects in remote machines are only references via handles, which are nvalid, if the underlying bridge connection gets closes). This is especially useful in the inspector tool.
	is still open. For example in the inspector tool.

	In this case, you should either "''Remove all Results in System''" (in the "''Test-Results''"-menu), and then perform a memory cleanup, or use one of the other maintenance functions from the debugging menu to close handles (i.e. "''Close all Sockets''", "''Close all Bridge Connections''", "''Close all Serial Connections''" etc.).		In this case, you should either "''Remove all Results in System''" (in the "''Test-Results''"-menu), and then perform a memory cleanup, or use one of the other maintenance functions from the debugging menu to close handles (i.e. "''Close all Sockets''", "''Close all Bridge Connections''", "''Close all Serial Connections''" etc.).

Cg: /* Memory Cleanup */

2016-09-09T11:32:32Z

Memory Cleanup

← Nächstältere Version		Version vom 9. September 2016, 11:32 Uhr
Zeile 21:		Zeile 21:
	=== Memory Cleanup ===		=== Memory Cleanup ===

	Under normal conditions, you don't have to care about expecco's memory: its underlying support system performs automatic memory management (garbage collection). This includes automatic finalization of objects which refer to operating system resources such as file handles, database-connections etc. However, these finalizations may happen quite delayed, due to the fact that the garbage collector is usually only invoked when running out of memory or when more memory is requested. This means, that if a file- or database handle has not been closed, but is also no longer used by a testSuite, that handle will be closed (and thereby freed) whenever the next garbage collect operation occurs. Which, if no memory is needed for some time, may happen quite delayed.		Under normal conditions, you don't have to care about expecco's memory: its underlying support system performs automatic memory management (garbage collection). This includes automatic finalization of objects which refer to operating system resources such as file handles, database-connections etc.

			However, these finalizations may happen quite delayed, due to the fact that the garbage collector is usually only invoked when running out of memory or when more memory is requested. This means, that if a file- or database handle has not been closed, but is also no longer used by a testSuite, that handle will be closed (and thereby freed) whenever the next garbage collect operation occurs. Which, if no memory is needed for some time, may happen quite delayed.

			Another situation in which handles are still referenced (and therefore not closed automatically) is when such handles are still present in an activity-log/trace. Because all data which was interchanged between steps is recorded there, handles may end up being recorded and therefore considered to be still "in-use" by the automatic memory management.

	This tool-function forces a garbage collect operation to be triggered immediately, and thereby freeing any unreferenced operating system resources. When those resources get collected, a finalize function is called automatically, which closes the associated operating system handle. Use this, if you have the feeling that the system is using many file, window, socket or other handles.		This tool-function forces a garbage collect operation to be triggered immediately, and thereby freeing any unreferenced operating system resources. When those resources get collected, a finalize function is called automatically, which closes the associated operating system handle. Use this, if you have the feeling that the system is using many file, window, socket or other handles.

	Notice: the automatic memory management can of course only free memory which is completely unreachable. This means that objects which are still referenced by other referenced objects will not be reclaimed. In expecco, one such "top level" referrer is usually the result log/execution trace of the previous execution(s). This is the storage you see when inspecting pin values after an execution. For example, if a socket or file handle is stored in this execution trace, AND this handle was not properly closed (either because the suite simply forgot to close it, or because the test was aborted and the suite provided no close in its post-action, then the handle might be stored in the log, and is therefore never closed automatically.		Notice: the automatic memory management can of course only free memory which is completely unreachable. This means that objects which are still referenced by other referenced objects will not be reclaimed. In expecco, one such "top level" referrer is usually the result log/execution trace of the previous execution(s).

⚫	In this case, you should either "Remove all Results in System" (in the "Test-Results"-menu), and then perform a memory cleanup, or use one of the other maintenance functions from the menu to close handles.
			This is the storage you see when inspecting pin values after an execution. For example, if a socket or file handle is stored in this execution trace, AND this handle was not properly closed (either because the suite simply forgot to close it, or because the test was aborted and the suite provided no close in its post-action), then the handle might be stored in the log, and is therefore never closed automatically.

			Notice that this behavior is not a bug: it is often very useful, to have external connections still open, when looking at the activity-log,
			because in many contexts you can inspect and interact with the connection if it
			is still open. For example in the inspector tool.

		⚫	In this case, you should either "''Remove all Results in System''" (in the "''Test-Results''"-menu), and then perform a memory cleanup, or use one of the other maintenance functions from the debugging menu to close handles (i.e. "''Close all Sockets''", "''Close all Bridge Connections''", "''Close all Serial Connections''" etc.).

Cg: /* Show All External Connections */

2014-12-19T00:00:42Z

Show All External Connections

← Nächstältere Version		Version vom 19. Dezember 2014, 00:00 Uhr
Zeile 1:		Zeile 1:
	=== Show ~~All~~ External Connections ===		=== Show all External Connections ===

	Opens an inspector on all external connections which possibly hold a handle to either a socket, pipe or serialPort.		Opens an inspector on all external connections which possibly hold a handle to either a socket, pipe or serialPort.

Cg: /* Show All External Connections */

2014-12-19T00:00:11Z

Show All External Connections

@@ Zeile 1: / Zeile 1: @@
 === Show All External Connections ===
-Opens an inspector on all external connections which possibly hold a handle to either a Socket, Pipe or SerialPort.
+Opens an inspector on all external connections which possibly hold a handle to either a socket, pipe or serialPort.
 === Memory Cleanup ===

Cg: /* Memory Cleanup */

2014-12-18T23:57:55Z

Memory Cleanup

← Nächstältere Version		Version vom 18. Dezember 2014, 23:57 Uhr
Zeile 1:		Zeile 1:
			=== Show All External Connections ===

			Opens an inspector on all external connections which possibly hold a handle to either a Socket, Pipe or SerialPort.


	=== Memory Cleanup ===		=== Memory Cleanup ===

Cg: Die Seite wurde neu angelegt: „=== Memory Cleanup === Under normal conditions, you don't have to care about expecco's memory: its underlying support system performs automatic memory managem…“

2014-12-18T23:55:34Z

Die Seite wurde neu angelegt: „=== Memory Cleanup === Under normal conditions, you don't have to care about expecco's memory: its underlying support system performs automatic memory managem…“

Neue Seite

=== Memory Cleanup ===

Under normal conditions, you don't have to care about expecco's memory: its underlying support system performs automatic memory management (garbage collection). This includes automatic finalization of objects which refer to operating system resources such as file handles, database-connections etc. However, these finalizations may happen quite delayed, due to the fact that the garbage collector is usually only invoked when running out of memory or when more memory is requested. This means, that if a file- or database handle has not been closed, but is also no longer used by a testSuite, that handle will be closed (and thereby freed) whenever the next garbage collect operation occurs. Which, if no memory is needed for some time, may happen quite delayed.

This tool-function forces a garbage collect operation to be triggered immediately, and thereby freeing any unreferenced operating system resources. When those resources get collected, a finalize function is called automatically, which closes the associated operating system handle. Use this, if you have the feeling that the system is using many file, window, socket or other handles.

Notice: the automatic memory management can of course only free memory which is completely unreachable. This means that objects which are still referenced by other referenced objects will not be reclaimed. In expecco, one such "top level" referrer is usually the result log/execution trace of the previous execution(s). This is the storage you see when inspecting pin values after an execution. For example, if a socket or file handle is stored in this execution trace, AND this handle was not properly closed (either because the suite simply forgot to close it, or because the test was aborted and the suite provided no close in its post-action, then the handle might be stored in the log, and is therefore never closed automatically.
In this case, you should either "Remove all Results in System" (in the "Test-Results"-menu), and then perform a memory cleanup, or use one of the other maintenance functions from the menu to close handles.

Back to [[Online_Documentation#Tools | Online Documentation]].