Getting "Value cannot be null" loading specific .tsperf files

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Unplanned

Last Updated: 21 Jul 2016 08:37 by ADMIN

ADMIN

Cody

Created on: 23 Oct 2015 20:19

Type: Bug Report

Getting "Value cannot be null" loading specific .tsperf files

In a customer supplied project and performance result set, 5 of the results are silently failing to load. When you look in the log you see:

Outer Exception Type: System.ArgumentNullException
     Message: Value cannot be null.
          Parameter name: key

From the users perspective he was expecting to see all 15 results, but can only see 5 of them. Test Studio did not report any errors to the user while loading the results. This is what I mean by "silently failing". It's not until you think to enable logging then look at the log do you see the error.

So this problem report is about two very closely related issues:
1) No error/warning is shown to the user when Test Studio failed to load specific .tsperf files
2) Why did Test Studio fail to load these specific result files?

The test project and result files will be added to the internal bug report.

1 comment

ADMIN

Daniel Djambov

Posted on: 09 Nov 2015 11:49

Telerik: the performance results are too big and cause Out Of Memory Exception when loaded, which is a problem in .Net addressing memory (does not relate to available physical memory of the machine). Our recommendation for such cases is to extend the Test Studio memory to use large addresses (over 2 GB), which will help loading bigger results. Here is an article how to configure Telerik.TestStudio.Desktop.exe to use large addresses on a 64 bit machine (http://docs.telerik.com/teststudio/knowledge-base/getting-out-of-memory-exception-errors). Please follow these instructions at the bottom of the page to overcome the OOM issue.

Note: our recommendation when configuring performance counters is not to use so many machine counters if not needed (30+ counters is not usually needed).

In the mean time we have filed an internal bug report to investigate further the opening of big performance results with huge number of counters and will update this feedback on the progress of our investigation.