Meanwhile I returned to sysAppLaunchCmdNormalLaunch. New emulator session did not help. Neither emulator restart.
>> Everything on except Beam > I'm not sure what option you're referring to here. There's no "Beam" anywhere in my .rc file, let alone that dialog. Sorry, I was a bit lazy. I meant Debug Options / Dialog Handling / Beam every 2 seconds... (Unimportant setting) ----- Original Message ----- From: "Keith Rollin" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Wednesday, September 03, 2003 11:29 PM Subject: RE: Emulator not detecting memory leaks > Debug Options: > Everything on except Beam I'm not sure what option you're referring to here. There's no "Beam" anywhere in my .rc file, let alone that dialog. > I don't know if there can be some connection, but the last > thing I was doing > before I noticed that the leaks are not reported, were tests > using custom > launch codes. (Set via CW debugging options.) Poser warns about memory leaks on a patch it places on SysAppExit. It's likely that the launch codes you're testing with don't include calling SysAppStartup and SysAppExit. If so, you won't get the leak messages. If you are continuing to not get the leak messages even with normal launch codes, then I wonder if some internal state in Poser got confused. But this would only occur if you continued to use the same .psf file over and over again. Is this the case? Have you tried creating a new session? (Ah, I see that my application has been approved, and that I have to run this executable that someone I don't know just sent me. Talk to you later!) -- Keith Rollin -- Palm OS Emulator engineer -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
