App issues with CE 5.0

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We have ported our application (9 exe's & numerous dll's) to CE 5.0 and have
found several interesting issues that appear to be unique to CE 5.0 (we
formerly ran CE 4.0 without these issues). I am wondering if anyone else
has experienced these problems.

1. Our app routinely starts threads that create and communicate with COM
objects. Some of these theads get destroyed and subsequently re-created in
normal operation. Although the threads get successly destroyed (indicated
by PB processes), the memory allocated during thread creation is not
released and a memory leak results. The memory leak is eliminated by
creating but not destroying threads.

2. During testing we found that there were repeatablie user input sequences
that resulted in exceptions and these exceptions were traced to ATL. So, we
replaced the ATL SDK and atlce400.dll files with those from CE 4.0 and
rebuilt the application and OS image. And, we have not experienced any
exceptions in our testing with these changes.






.

Relevant Pages

  • RE: Can this cause memory leak ?
    ... No memory leak to worry about. ... it is inefficient and bad practice to catch exceptions ... during the normal flow of your code. ... > But I worry there is memory leak for lack the Deletecall. ...
    (microsoft.public.vc.language)
  • Re: SerialPort Class
    ... I've experienced sudden stops (no exceptions) due to a memory leak. ... method until a 'special character is received or a timeout elapses. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Allocatable Components of Derived Type
    ... One exception I guess is an allocatable array declared in a subroutine ... There are *NO* exceptions. ... Such a case will not cause a memory leak, ... If you try to allocate the array again without ...
    (comp.lang.fortran)
  • Re: Unloading an AppDomain
    ... I'd be wary of creating and destroying a large quantity of ... > appdomains in an application that was intended to remain running for very ... Would that still qualify for a memory leak?? ...
    (microsoft.public.dotnet.framework)
  • Issues with CE 5.0 ATL Accelerator Table
    ... After comparing the ATL of the two versions, ... The destroying of the accelerator is then done in atlctl.h if necessary. ... assignment. ... the CAxHostWindow class eliminates the exceptions seen. ...
    (microsoft.public.windowsce.app.development)