locked
windows mobile classic app crash / mem leak problem RRS feed

  • Question

  • I'm working for a company that has deployed a software I have written to windows mobile classic running on an iPac device.  The application runs in the activeX Flash Player control from Adobe.  It tranditionally used Flash Remoting to connect to a server and exchange information.  This application runs fine on a number of OS's and devices, but this is it's first deployment into windows mobile.

    The application experiences intermitant crashes.  Additionally if I look at the "memory" panel it shows the PNYSICAL STORAGE decreasing rapidly.

    I have removed the flash remoting, under the theory that it had a broken implementation in the Flash 7 player for winmobile, and substituted a simple http GET routine to retrieve data.

    Still the application crashes.

    I'm not exactly sure where to go from here.  I believe something in the OS is set up wrong, or broken in such a way that the application is leaking memory.  But I know the app is solid since it runs perfectly well on several other platforms.

    Is there something I can look at in the OS?  Some kind of file paging or caching that might be going on?  I'm not an OS expert and have essentially no experience in windows mobile which is making my attempts to debug this issue quite difficult.

    Any help or suggestions are appreciated.
    Wednesday, September 30, 2009 7:42 PM

Answers

  • Hi,

    You may be interested in the series of blog posts on Memory by Raffaele :-

    http://blogs.msdn.com/raffael/archive/tags/Memory/default.aspx

    Hope this helps.

    Paul Diston
    http://www.smartmobiledevice.co.uk/
    • Marked as answer by warrentang Wednesday, October 7, 2009 2:59 AM
    Wednesday, September 30, 2009 9:31 PM
  • One possible source of the memory leaks in such application is the implementation of the ActiveX host. Look for things like not calling SysFreeString after the calls that retrieve strings from ActiveX using [out] BSTR* parameters. Also see if there are interfaces that are addrefed and not released
    Alex Feinman. MVP .NET Compact Framework
    • Marked as answer by warrentang Wednesday, October 7, 2009 2:59 AM
    Wednesday, September 30, 2009 10:32 PM

All replies

  • Hi,

    You may be interested in the series of blog posts on Memory by Raffaele :-

    http://blogs.msdn.com/raffael/archive/tags/Memory/default.aspx

    Hope this helps.

    Paul Diston
    http://www.smartmobiledevice.co.uk/
    • Marked as answer by warrentang Wednesday, October 7, 2009 2:59 AM
    Wednesday, September 30, 2009 9:31 PM
  • One possible source of the memory leaks in such application is the implementation of the ActiveX host. Look for things like not calling SysFreeString after the calls that retrieve strings from ActiveX using [out] BSTR* parameters. Also see if there are interfaces that are addrefed and not released
    Alex Feinman. MVP .NET Compact Framework
    • Marked as answer by warrentang Wednesday, October 7, 2009 2:59 AM
    Wednesday, September 30, 2009 10:32 PM