Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 1860 - Application Verifier Warning SetProcessWorkingSetSize Incorrect Value
Summary: Application Verifier Warning SetProcessWorkingSetSize Incorrect Value
Status: IN_PROGRESS
Alias: None
Product: ActiveX TeeChart
Classification: Unclassified
Component: Visual C++ (show other bugs)
Version: TeeChart Pro Activex Control v2014 v2014.0.0.0 Release
Hardware: PC Windows
: --- critical
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-11 15:32 EDT by Cerner
Modified: 2017-05-31 04:14 EDT (History)
1 user (show)

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:

Attachments
Sample C++ project to repro the issue (202.77 KB, application/x-zip-compressed)
2017-05-17 18:35 EDT, Cerner 		Details
Updated version of the test app to correct header files (142.40 KB, application/x-zip-compressed)
2017-05-25 10:45 EDT, Cerner 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cerner 2017-05-11 15:32:04 EDT 
While using WinDbg and Application Verifier (x64) we see a verifier stop message for the incorrect usage of SetProcessWorkingSetSize function call. Application verifier message details:

APPLICATION_VERIFIER_DANGEROUS_INVALID_MINIMUM_PROCESS_WORKING_SIZE (105)
SetProcessWorkingSetSize is called with MinimumWorkingSetSize = 0xFFFFFFFF.
Please use MinimumWorkingSetSize = (SIZE_T) -1.

This AppVerify messages seems to suggest Teechart is calling SetProcessWorkingSetSize using a value of 0xFFFFFFFF instead of (SIZE_T)-1. In a x64 process 0xFFFFFFFF is a valid large value and not -1. Will you please confirm the use of the SetProcessWorkingSetSize in TeeChart is correct?

Steps to Reproduce:
1. Create a small x64 VC++ test application using TeeChart201464.ocx.
2. Add the test application image (exe) to Application Verifer x64 with the basic option checked.
3. Use WinDbg x64 to run the test application.
4. Notice on create of the control an application verifier stop 105 will occur.
Comment 1 Cerner 2017-05-11 15:44:16 EDT 
What TeeChart version are you using?
- File name: TeeChart201464.ocx
- Product Name: TeeChart Pro ActiveX Control v2014
- File Version: 2014.0.0.1
- Product Version: 2014.0.0.0

What IDE are you using?
 - Visual Studio 2015 Enterprise
 
What language are you programming with?
- Visual C++ / MFC / x64 project type

What exact OS are you running?
- Multiple: Windows 10 64-bit / Windows 2012 Server 64-bit
Comment 2 Cerner 2017-05-12 19:36:21 EDT 
Sorry we missed a repro step:

Revised Steps to Reproduce:
1. Create a small x64 VC++ test application using TeeChart201464.ocx.
2. Add the test application image (exe) to Application Verifer x64 with the basic option checked.
3. Expand Miscellaneous and check DangerousAPIs.
4. Select Save.
5. Use WinDbg x64 to run the test application.
6. Notice on create of the control an application verifier stop 105 will occur.
Comment 3 Cerner 2017-05-17 18:35:56 EDT 
Created attachment 762 [details]
Sample C++ project to repro the issue
Comment 4 Cerner 2017-05-22 17:57:07 EDT 
What is the expected review and feedback cycle for bugs?
Comment 5 Cerner 2017-05-25 10:45:10 EDT 
Created attachment 767 [details]
Updated version of the test app to correct header files
Comment 6 Cerner 2017-05-30 14:52:41 EDT 
Tested version 2017.0.0 and the issue is still present.