Forum Discussion
AlexeyKryuchkov
13 years agoSmartBear Alumni (Retired)
Hi Muhammad,
Did LoadComplete show its dumper window when it crashed? If it did, there should be dmp files in the "C:\Users\<username>\AppData\Local\SmartBear\LoadComplete\1.0\Logs\" (in Windows Vista or later) or "C:\Documents and Settings\<username>\Local Settings\Application Data\SmartBear\LoadComplete\1.0\Logs\" (in other versions of Windows) folder. Please send us the files whose filename corresponds to the date and time of the crashes - we'll analyze them.
If LoadComplete didn't show its dumper window, please collect some additional information about the issue in the following way:
1. Download AQtime Standard, which is our free profiling tool.
2. Install the tool and run it.
3. Select the 'File | New Project From Module...' main menu item.
4. In the Open File dialog, select the "<Program Files>\SmartBear\LoadComplete\Bin\LoadComplete.exe" file and click Open.
5. Take a look at the AQtime toolbar - there is a combo box. Open it and select the "Tracing | Exception Trace Profiler" item.
6. Select the "Options | Options..." main menu command - the Options dialog will appear.
7. Set the "Profiling Time | Event View | General | Exceptions | Depth shown" setting to 100 and click OK.
8. Click the Run toolbar button (the green arrow) or press F5 to start profiling.
9. AQtime will start LoadComplete and trace all the exceptions that will occur in the application until it is closed.
10. Reproduce the problem in LoadComplete.
11. After the problem occurs, right-click somewhere within the Event View panel (it is opened by default at the bottom of AQtime's window) and select the 'Save All...' item.
12. Save the panel's contents to an HTML file and send me the file via our [url=]Contact Support form[/url].
Please collect additional information on the issue in the following way:
1. Download the Debugging Tools for Windows package and install it.
2. Create the "C:\dumps" folder.
3. Run "C:\Program Files\Debugging Tools for Windows (x86)\windbg.exe" (on 32-bit versions of Windows) or "C:\Program Files (x86)\Debugging Tools for Windows (x86)\windbg.exe" (on 64-bit versions of Windows) as Administrator.
4. Choose WinDbg's "File | Open Executable..." main menu item and choose the tested application's executable in the dialog that appears.
5. Choose No in the dialog that suggests saving information for the workspace. After that, WinDbg will start LoadComplete and trace the exceptions that occur in it.
5. Execute the following command in WinDbg's Command window:
gn; .dump /m /u C:\dumps\.dmp; z(1>0)
WinDbg will automatically create memory dumps when exceptions occur.
6. When LoadComplete hangs, click Break (or press "Ctrl + Break"). WinDbg will immediately create a memory dump for the break instruction exception.
7. Wait for a minute and repeat step 6.
8. Click somewhere within the Command window to select it and save its contents to "C:\dumps\output.txt" files by choosing the "Edit | Write Window Text to File..." main menu item and specifying this file in the dialog that appears.
9. Pack the "C:\dumps" folder and send us the archive using the [url=]Contact Support form[/url].
Pack the folders containing your TestComplete project suite and LoadComplete test project along with execution logs that demonstrate the difference and send us the archives using our Contact Support form. We'll try to determine the cause of such a difference.
Again, we'll need both the TestComplete project suite and the LoadComplete test project along with execution logs that will demonstrate the difference - please send them to us using our Contact Support form.
There's no way to do this. If you think that test results generated by LoadComplete lack some crucial information, please let us know - describe the information you need and why it is needed.
BTW, if you need personal assistance, you can submit separate support cases using our Contact Support form. Also, please create an individual ticket for each request - this will help us track queries in a better way.
LoadCompleted Crashed - 2 times for each scenario
TestComplete Crashed - No
Did LoadComplete show its dumper window when it crashed? If it did, there should be dmp files in the "C:\Users\<username>\AppData\Local\SmartBear\LoadComplete\1.0\Logs\" (in Windows Vista or later) or "C:\Documents and Settings\<username>\Local Settings\Application Data\SmartBear\LoadComplete\1.0\Logs\" (in other versions of Windows) folder. Please send us the files whose filename corresponds to the date and time of the crashes - we'll analyze them.
If LoadComplete didn't show its dumper window, please collect some additional information about the issue in the following way:
1. Download AQtime Standard, which is our free profiling tool.
2. Install the tool and run it.
3. Select the 'File | New Project From Module...' main menu item.
4. In the Open File dialog, select the "<Program Files>\SmartBear\LoadComplete\Bin\LoadComplete.exe" file and click Open.
5. Take a look at the AQtime toolbar - there is a combo box. Open it and select the "Tracing | Exception Trace Profiler" item.
6. Select the "Options | Options..." main menu command - the Options dialog will appear.
7. Set the "Profiling Time | Event View | General | Exceptions | Depth shown" setting to 100 and click OK.
8. Click the Run toolbar button (the green arrow) or press F5 to start profiling.
9. AQtime will start LoadComplete and trace all the exceptions that will occur in the application until it is closed.
10. Reproduce the problem in LoadComplete.
11. After the problem occurs, right-click somewhere within the Event View panel (it is opened by default at the bottom of AQtime's window) and select the 'Save All...' item.
12. Save the panel's contents to an HTML file and send me the file via our [url=]Contact Support form[/url].
LoadComplete Hanged during Report Generation - several times
TestComplete Hanged during Report Generation - None
Please collect additional information on the issue in the following way:
1. Download the Debugging Tools for Windows package and install it.
2. Create the "C:\dumps" folder.
3. Run "C:\Program Files\Debugging Tools for Windows (x86)\windbg.exe" (on 32-bit versions of Windows) or "C:\Program Files (x86)\Debugging Tools for Windows (x86)\windbg.exe" (on 64-bit versions of Windows) as Administrator.
4. Choose WinDbg's "File | Open Executable..." main menu item and choose the tested application's executable in the dialog that appears.
5. Choose No in the dialog that suggests saving information for the workspace. After that, WinDbg will start LoadComplete and trace the exceptions that occur in it.
5. Execute the following command in WinDbg's Command window:
gn; .dump /m /u C:\dumps\.dmp; z(1>0)
WinDbg will automatically create memory dumps when exceptions occur.
6. When LoadComplete hangs, click Break (or press "Ctrl + Break"). WinDbg will immediately create a memory dump for the break instruction exception.
7. Wait for a minute and repeat step 6.
8. Click somewhere within the Command window to select it and save its contents to "C:\dumps\output.txt" files by choosing the "Edit | Write Window Text to File..." main menu item and specifying this file in the dialog that appears.
9. Pack the "C:\dumps" folder and send us the archive using the [url=]Contact Support form[/url].
LoadComplete execution time for Scenario 1 with 50 VU = 10m
TestComplete execution time for Scenario 1 with 50 VU = 5m
LoadComplete execution time for Scenario2 with 50 VU = 27m
TestComplete execution time for Scenario 2 with 50 VU = 5m
Pack the folders containing your TestComplete project suite and LoadComplete test project along with execution logs that demonstrate the difference and send us the archives using our Contact Support form. We'll try to determine the cause of such a difference.
I have provided Server Credentials to LoadComplete and TestComplete - Credentials not accepted by LoadComplete still giving me the same warning message, but these credentials were accepted by TestComplete.
Again, we'll need both the TestComplete project suite and the LoadComplete test project along with execution logs that will demonstrate the difference - please send them to us using our Contact Support form.
New reports are good but what if i want to generate the same report as i have in TestComplete?
There's no way to do this. If you think that test results generated by LoadComplete lack some crucial information, please let us know - describe the information you need and why it is needed.
BTW, if you need personal assistance, you can submit separate support cases using our Contact Support form. Also, please create an individual ticket for each request - this will help us track queries in a better way.
Related Content
- 2 years ago
- 2 years ago
- 3 years ago
Recent Discussions
- 9 months ago
- 2 years ago
- 3 years ago
- 3 years ago