Product Version: 3.0 & 3.1
Operating System: Microsoft* Windows* XP, Microsoft* Vista*, Microsoft* 2003 Server
Problem Description:We recently received several problem reports. If the size of user's application is extreme big, the user complained that the application (launched by Thread Profiler) ran slowly.
Cause:Thread Profiler's engine uses 600MB (default) in the heap. If the application also needs to consume higher memory space in the heap and the user works on lower hardware (memory) configuration, it causes this problem
Resolution: Use "Configuration Intel® Thread Checker" -> "Execution" tab -> "Limit the size of the heap of the heap used by the analysis engine to [ ] MB", adjust to smaller number. Note when Thread Checker reaches the memory limit, it may discard older statistics, causing some loss of results.
[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]