|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by atomicgs12 in Windows Mobile (Pocket PC / Win CE) Operating Systems
I have a rather complex windows CE application that uses some 30+ threads. Recently I noticed a memory leak when I added a new CreateThread to my app. I put this CreateThread in a loop, for testing, and noticed that about every third CreateThread my app was leaking some 4096 bytes, via GlobalMemoryStatus. I put this same createthread in another shorter app, ran the test loop, and had no memory leak via the GlobalMemoryStatus call. I have tried ever combination of CreateThread, WaitForSingleObject and CloseHandle that I can think of and still the leak persists. This test thread is just an empty function that immediately returns a 1. Also this complex app where the leak is taking place has a mixture of AFXBeginThread and CreateThread. So I guess my question is has anybody seen this 4096 memory leak before? Could this leak be related to some other CreateThread issue somewhere else in the code? Any ideas would be appreciated.
20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625