Join 34,000+ subscribers and receive articles from our
blog about software quality, testing, QA and security.

SmartInspect 3.2 EAP (beta) available


#1

We just uploaded a new Early Access Program build of SmartInspect 3.2 to our customer portal. Besides adding some often requested features to the Console and logging libraries, we made some major changes to the SmartInspect Console in how it loads and processes log files, reducing the memory usage during log file loading drastically and making it faster in general.

We’ve also upgraded the Console to make use of the latest development tools and third-party components available, integrating it better with Windows Vista and preparing it for Windows 7. Because of these changes, we need your help in testing this new release and would really appreciate any feedback you can provide.

What’s New

The following list displays all changes of the SmartInspect 3.2.0 release at a glance. The changes are divided into multiple sections (libraries, Console and so on). Please note that SmartInspect 3.2.0 is a beta release and is made available as part of our EAP (Early Access Program).

Libraries:

[list=]
[
]Added: Connection variables for automatically replacing variables in a connection string[/]
[
]Added: Width format option for text protocol pattern string[/]
[
]Added: Custom timestamp format for text protocol pattern string (platform-specific)[/]
[
]Added: Exception.StackTrace support for LogException (Delphi only)[/]
[
]Added: Support for protocol objects in addition to raw streams in the Dispatch method of the memory protocol (e.g., for sending the packet queue directly to a Console)[/]
[
]Fixed: Potential memory leak in memory protocol (Delphi only)[/*]
[/list]

Console:
[list=]
[
]Added: ‘View | Create View’ feature for quickly opening new filtered views[/]
[
]Added: /configdir command line option for overriding the configuration directory[/]
[
]Added: /pipename command line option for overriding the pipe name of the named pipe server[/]
[
]Added: ‘Navigate | Toggle Bookmark’ now indicates whether bookmarks are already in use[/]
[
]Added: ‘Navigate | Go to Bookmark’ now signals the bookmark states by disabling unused bookmarks[/]
[
]Added: Middle-click on a view now deletes it (as in most web browsers)[/]
[
]Changed: Clear View Rules has been replaced with the View Filters Enabled toggle option[/]
[
]Changed: Improved view performance when displaying large Log Entry titles[/]
[
]Changed: Improved performance of title and data viewers[/]
[
]Changed: Improved log file loading performance and reduced memory consumption[/]
[
]Changed: TCP and named pipe server error messages now include the TCP port and pipe name (to simplify troubleshooting)[/]
[
]Fixed: Improved docking experience and performance under Windows Vista[/]
[
]Fixed: A drawing related resizing bug under Windows Vista (under certain circumstances, the views would not be painted correctly)[/]
[
]Fixed: Improved Console contrast and coloring under Windows Vista[/]
[
]Fixed: Possible Access Violation when failing to start the named pipe server[/]
[
]Fixed: Error handling in TCP and named pipe servers after changing the options[/*]
[/list]

Download

To download this new EAP release, please login to our customer portal My Gurock.com with your account information. Please provide feedback to this new version in our Early Access Program forum or via email. Please also see our blog for information on how to install EAP versions side-by-side with release versions.


#2

Hello,

Is this change (reduced memory consumption) a solution for problem we were talking about in this thread ?

I tried to use new console, but I after several thousands of packets it takes more than 200MB of memory.

best regards
Piotr Rezmer


#3

Hello Piotr,

we mainly reduced memory consumption while loading log files and thus reducing memory peaks. That means that you are able to load larger log files than before, but it does not mean that log entries consume less memory after being loaded.

However, we are investigating and planning to integrate two techniques to reduce the consumed memory of logging data in the Console. In your case (multiple thousands of packets taking more than 200MB), it sounds like you have quite a bit of data attached to log entries, is this correct?

We are looking into storing/moving attached data to disk instead of RAM, but we have just begun investigating this and it’s still too early to say if this gets integrated into the product or not.


#4

Hello,

I think it would be quite enough to add an option of maximum entries within console Tools/Options/General tab.

best regards
Piotr Rezmer


#5

Piotr,

we are looking into adding such an option or something similar, but it isn’t as easy it sounds at first. For example, instead of a log entry limit, a memory consumption limit would probably be more appropriate (some log entries have a lot of data attached, others have none). Additionally to having such an option, it would also be needed to add some kind of auto-purge functionality, so that old log entries are automatically deleted.