ToolsMenuFunctions/en - Versionsgeschichte

Cg: /* Memory Cleanup */

2019-10-17T21:30:49Z

Memory Cleanup

← Nächstältere Version		Version vom 17. Oktober 2019, 21:30 Uhr
Zeile 35:		Zeile 35:
	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.		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,		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 invalid, if the underlying bridge connection gets closed). This is especially useful in the inspector tool.		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 invalid, if the underlying bridge connection gets closed). This is especially useful for UI connections and 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: /* Close all Serial Connections */

2019-10-17T21:28:53Z

Close all Serial Connections

← Nächstältere Version		Version vom 17. Oktober 2019, 21:28 Uhr
Zeile 15:		Zeile 15:
	=== Close all Serial Connections ===		=== Close all Serial Connections ===

	Tears down ~~leftover~~ serial connections		Tears down open serial connections

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

Cg: /* Close all Socket Connections */

2019-10-17T21:28:41Z

Close all Socket Connections

← Nächstältere Version		Version vom 17. Oktober 2019, 21:28 Uhr
Zeile 11:		Zeile 11:
	=== Close all Socket Connections ===		=== Close all Socket Connections ===

	Tears down ~~leftover~~ socket connections (interprocess communication).		Tears down all open socket connections (interprocess communication).

	=== Close all Serial Connections ===		=== Close all Serial Connections ===

Cg: /* Shut Down Bridge Connections */

2019-10-17T21:27:54Z

Shut Down Bridge Connections

← Nächstältere Version		Version vom 17. Oktober 2019, 21:27 Uhr
Zeile 7:		Zeile 7:
	=== Shut Down Bridge Connections ===		=== Shut Down Bridge Connections ===

	Tears down leftover Java Bridge connections.		Tears down leftover Java, DotNet, Python, NodeJS and C Bridge connections.

	=== Close all Socket Connections ===		=== Close all Socket Connections ===

Cg am 3. September 2019 um 09:06 Uhr

2019-09-03T09:06:41Z

← Nächstältere Version		Version vom 3. September 2019, 09:06 Uhr
Zeile 1:		Zeile 1:
	These functions are found in the "Extras"->"Debugging" menu.		These functions are found in the "''Extras''" → "''Debugging''" menu.

	=== Show all External Connections ===		=== Show all External Connections ===

Mawalch am 5. Juni 2017 um 11:56 Uhr

2017-06-05T11:56:20Z

Cg: /* Show all External Connections */

2016-12-12T17:35:57Z

Show all External Connections

← Nächstältere Version		Version vom 12. Dezember 2016, 17:35 Uhr
Zeile 3:		Zeile 3:
	=== 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. The inspectors presents a list of those connections and a menu function to close them selectively (by ~~evaluatng~~ "self close" in the inspector). Notice, that all open streams are shown, including stderr and stdout. Do not close those.		Opens an inspector on all external connections which possibly hold a handle to either a socket, pipe or serialPort. The inspectors presents a list of those connections and a menu function to close them selectively (via the menu or by evaluating "<code>self close</code>" in the inspector). Notice, that all open streams are shown, including stderr and stdout. Do not close those.

	=== Shut Down Bridge Connections ===		=== Shut Down Bridge Connections ===

Cg: /* Show all External Connections */

2016-12-12T17:35:27Z

Show all External Connections

← Nächstältere Version		Version vom 12. Dezember 2016, 17:35 Uhr
Zeile 3:		Zeile 3:
	=== 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. The inspectors presents a list of those connections and a menu function to close them selectively.		Opens an inspector on all external connections which possibly hold a handle to either a socket, pipe or serialPort. The inspectors presents a list of those connections and a menu function to close them selectively (by evaluatng "self close" in the inspector). Notice, that all open streams are shown, including stderr and stdout. Do not close those.

	=== Shut Down Bridge Connections ===		=== Shut Down Bridge Connections ===

Cg: /* Show all External Connections */

2016-12-12T17:30:41Z

Show all External Connections

← Nächstältere Version		Version vom 12. Dezember 2016, 17:30 Uhr
Zeile 3:		Zeile 3:
	=== 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. The inspectors presents a list of those connections and a menu function to close them selectively.

	=== Shut Down Bridge Connections ===		=== Shut Down Bridge Connections ===

Cg am 12. Dezember 2016 um 17:29 Uhr

2016-12-12T17:29:51Z

← Nächstältere Version		Version vom 12. Dezember 2016, 17:29 Uhr
Zeile 1:		Zeile 1:
			These functions are found in the "Extras"->"Debugging" menu.

	=== Show all External Connections ===		=== Show all External Connections ===

← Nächstältere Version		Version vom 5. Juni 2017, 11:56 Uhr
Zeile 7:		Zeile 7:
	=== Shut Down Bridge Connections ===		=== Shut Down Bridge Connections ===

	Tears down leftover ~~JavaBridge~~ connections.		Tears down leftover Java Bridge connections.

	=== Close all Socket Connections ===		=== Close all Socket Connections ===
Zeile 23:		Zeile 23:
	=== 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.		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.		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.
Zeile 31:		Zeile 31:
	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).		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.		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,		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.		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 invalid, if the underlying bridge connection gets closed). 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.).		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.).