![]() | Steema Issues DatabaseNote: 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. |
| Summary: | Application Verifier Warning SetProcessWorkingSetSize Incorrect Value | ||
|---|---|---|---|
| Product: | ActiveX TeeChart | Reporter: | Cerner <blake.howard> |
| Component: | Visual C++ | Assignee: | Steema Issue Manager <issuemanager> |
| Status: | IN_PROGRESS --- | ||
| Severity: | critical | CC: | sandra |
| Priority: | --- | ||
| Version: | TeeChart Pro Activex Control v2014 v2014.0.0.0 Release | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows | ||
| Chart Series: | --- | Delphi / C++ Builder RAD IDE Version: | |
| Attachments: |
Sample C++ project to repro the issue
Updated version of the test app to correct header files |
||
|
Description
Cerner
2017-05-11 15:32:04 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 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. Created attachment 762 [details]
Sample C++ project to repro the issue
What is the expected review and feedback cycle for bugs? Created attachment 767 [details]
Updated version of the test app to correct header files
Tested version 2017.0.0 and the issue is still present. |