|
|
You're in the
dotnet compact framework
group:quit unexpectedly
dotnet compact framework:
Our app got a long-term headache bug, that is our App sometimes quit unexpectedly without any warning. We heard that if installing SP3, everything is OK. But that's not true. Even installing SP3, our app still quit. We use a tool for automatically test 1 event load form, and write to log file to check in detail. The test report is as follows: 1) Hardware PDA Client machine: Pocket Loox/ FLX3AW CPU: Intel PXA 255 400MHz Memory: RAM 128M and ROM 64 M OS: Window Mobile 2003 software for Pocket PC Database: MS SQL CE 2) Software Test: Pocket PC Controller Professional Version 4.12 Delopement: VB.NET compact framework 3) Metrics Total number tests: 250 Total number of quiting unexpectedly: 18 Test place: event load form of a specific form 4) Average Memory(GlobalStatusMemory API function) MemoryLoad: 46 TotalPhysical: 51.859375 AvailablePhysical: 28.21875 TotalPageFile: 0 AvailPageFile: 0 TotalVirtual: 32 AvailVirtual: 22.4375 5) Result It quit in any place in load form event, even at the end of function Load_Form We think of 4 capabilities: - Our App has a serious bug ? - Memory isn't enough ? - Window Mobile 2003 has a problem ? - Pocket PC Fujitsu device has a problem Any help to light up for us? Thanks, KNC
Hello, I have the same problem and found a ay to fix it, in my application
it was because of PInvoke to native functions. :) Does your application PInvoke to native functions? If does, so try to find out another solution to avoid PInvoke [quoted text, click to view] "KNC" <khanh@glassegg.com> wrote in message news:1112941264.015260.288950@f14g2000cwb.googlegroups.com... > hi all, > > Our app got a long-term headache bug, that is our App sometimes quit > unexpectedly without any warning. We heard that if installing SP3, > everything is OK. But that's not true. Even installing SP3, our app > still quit. > We use a tool for automatically test 1 event load form, and write to > log file to check in detail. The test report is as follows: > > 1) Hardware > PDA Client machine: Pocket Loox/ FLX3AW > CPU: Intel PXA 255 400MHz > Memory: RAM 128M and ROM 64 M > OS: Window Mobile 2003 software for Pocket PC > Database: MS SQL CE > > 2) Software > Test: Pocket PC Controller Professional Version 4.12 > Delopement: VB.NET compact framework > > 3) Metrics > Total number tests: 250 > Total number of quiting unexpectedly: 18 > Test place: event load form of a specific form > > 4) Average Memory(GlobalStatusMemory API function) > > MemoryLoad: 46 > TotalPhysical: 51.859375 > AvailablePhysical: 28.21875 > TotalPageFile: 0 > AvailPageFile: 0 > TotalVirtual: 32 > AvailVirtual: 22.4375 > > > 5) Result > It quit in any place in load form event, even at the end of > function Load_Form > > We think of 4 capabilities: > > - Our App has a serious bug ? > - Memory isn't enough ? > - Window Mobile 2003 has a problem ? > - Pocket PC Fujitsu device has a problem > > > Any help to light up for us? > Thanks, > KNC >
If the function you are P/Invoking has a direct managed equivalent then of
course you should use that instead, but especially with the Compact Framework there are times when you need to use P/Invoke because the functionality is not included in the standard class libraries.Do not forget that at some point all of the managed classes are calling down to the underlying OS for their functionality. There are a couple of possible reasons why your app may die under continuous P/Invoking, perhaps your P/Invoke definitions are wrong, perhaps you are not correctly handling an error condition, or perhaps you are not correctly allocating or freeing native memory. If you can pinpoint a specific function then post your P/Invoke declaration and code snippet of it in use and we can advise further. Peter -- Peter Foot Windows Embedded MVP http://www.inthehand.com | http://blog.opennetcf.org/pfoot/ [quoted text, click to view] "McFar" <_NO_NO__REMOVE_@6784.com> wrote in message news:eFxIUlCPFHA.3292@TK2MSFTNGP12.phx.gbl... >I am not sure that exception handling will help here.... > I posted an example of simple application here a couple of weeks ago, that > does nothing just PInvokes huge number of times in a row > and the application just disappeared, none exception, none message, just > disappeared.... > So I supposed that it is a PInvoke problem and replaced all the PInvoke > calls onto managed > functions, the application works fine now... > > "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message > news:OQAK9PCPFHA.2736@TK2MSFTNGP09.phx.gbl... >> Or use exception handling. There's no reason top avoid P/Invokes just >> becasue you fear them. >> >> -Chris >> >> >> >> "McFar" <_NO_NO__REMOVE_@6784.com> wrote in message >> news:uStfM$APFHA.2468@tk2msftngp13.phx.gbl... >> > Hello, I have the same problem and found a ay to fix it, in my > application >> > it was because of >> > PInvoke to native functions. :) >> > >> > Does your application PInvoke to native functions? If does, so try to > find >> > out another solution to avoid PInvoke >> > >> > >> > "KNC" <khanh@glassegg.com> wrote in message >> > news:1112941264.015260.288950@f14g2000cwb.googlegroups.com... >> >> hi all, >> >> >> >> Our app got a long-term headache bug, that is our App sometimes quit >> >> unexpectedly without any warning. We heard that if installing SP3, >> >> everything is OK. But that's not true. Even installing SP3, our app >> >> still quit. >> >> We use a tool for automatically test 1 event load form, and write to >> >> log file to check in detail. The test report is as follows: >> >> >> >> 1) Hardware >> >> PDA Client machine: Pocket Loox/ FLX3AW >> >> CPU: Intel PXA 255 400MHz >> >> Memory: RAM 128M and ROM 64 M >> >> OS: Window Mobile 2003 software for Pocket PC >> >> Database: MS SQL CE >> >> >> >> 2) Software >> >> Test: Pocket PC Controller Professional Version 4.12 >> >> Delopement: VB.NET compact framework >> >> >> >> 3) Metrics >> >> Total number tests: 250 >> >> Total number of quiting unexpectedly: 18 >> >> Test place: event load form of a specific form >> >> >> >> 4) Average Memory(GlobalStatusMemory API function) >> >> >> >> MemoryLoad: 46 >> >> TotalPhysical: 51.859375 >> >> AvailablePhysical: 28.21875 >> >> TotalPageFile: 0 >> >> AvailPageFile: 0 >> >> TotalVirtual: 32 >> >> AvailVirtual: 22.4375 >> >> >> >> >> >> 5) Result >> >> It quit in any place in load form event, even at the end of >> >> function Load_Form >> >> >> >> We think of 4 capabilities: >> >> >> >> - Our App has a serious bug ? >> >> - Memory isn't enough ? >> >> - Window Mobile 2003 has a problem ? >> >> - Pocket PC Fujitsu device has a problem >> >> >> >> >> >> Any help to light up for us? >> >> Thanks, >> >> KNC >> >> >> > >> > >> >> > >
I am not sure that exception handling will help here....
I posted an example of simple application here a couple of weeks ago, that does nothing just PInvokes huge number of times in a row and the application just disappeared, none exception, none message, just disappeared.... So I supposed that it is a PInvoke problem and replaced all the PInvoke calls onto managed functions, the application works fine now... [quoted text, click to view] "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message news:OQAK9PCPFHA.2736@TK2MSFTNGP09.phx.gbl... > Or use exception handling. There's no reason top avoid P/Invokes just > becasue you fear them. > > -Chris > > > > "McFar" <_NO_NO__REMOVE_@6784.com> wrote in message > news:uStfM$APFHA.2468@tk2msftngp13.phx.gbl... > > Hello, I have the same problem and found a ay to fix it, in my application > > it was because of > > PInvoke to native functions. :) > > > > Does your application PInvoke to native functions? If does, so try to find > > out another solution to avoid PInvoke > > > > > > "KNC" <khanh@glassegg.com> wrote in message > > news:1112941264.015260.288950@f14g2000cwb.googlegroups.com... > >> hi all, > >> > >> Our app got a long-term headache bug, that is our App sometimes quit > >> unexpectedly without any warning. We heard that if installing SP3, > >> everything is OK. But that's not true. Even installing SP3, our app > >> still quit. > >> We use a tool for automatically test 1 event load form, and write to > >> log file to check in detail. The test report is as follows: > >> > >> 1) Hardware > >> PDA Client machine: Pocket Loox/ FLX3AW > >> CPU: Intel PXA 255 400MHz > >> Memory: RAM 128M and ROM 64 M > >> OS: Window Mobile 2003 software for Pocket PC > >> Database: MS SQL CE > >> > >> 2) Software > >> Test: Pocket PC Controller Professional Version 4.12 > >> Delopement: VB.NET compact framework > >> > >> 3) Metrics > >> Total number tests: 250 > >> Total number of quiting unexpectedly: 18 > >> Test place: event load form of a specific form > >> > >> 4) Average Memory(GlobalStatusMemory API function) > >> > >> MemoryLoad: 46 > >> TotalPhysical: 51.859375 > >> AvailablePhysical: 28.21875 > >> TotalPageFile: 0 > >> AvailPageFile: 0 > >> TotalVirtual: 32 > >> AvailVirtual: 22.4375 > >> > >> > >> 5) Result > >> It quit in any place in load form event, even at the end of > >> function Load_Form > >> > >> We think of 4 capabilities: > >> > >> - Our App has a serious bug ? > >> - Memory isn't enough ? > >> - Window Mobile 2003 has a problem ? > >> - Pocket PC Fujitsu device has a problem > >> > >> > >> Any help to light up for us? > >> Thanks, > >> KNC > >> > > > > > >
Or use exception handling. There's no reason top avoid P/Invokes just
becasue you fear them. -Chris [quoted text, click to view] "McFar" <_NO_NO__REMOVE_@6784.com> wrote in message news:uStfM$APFHA.2468@tk2msftngp13.phx.gbl... > Hello, I have the same problem and found a ay to fix it, in my application > it was because of > PInvoke to native functions. :) > > Does your application PInvoke to native functions? If does, so try to find > out another solution to avoid PInvoke > > > "KNC" <khanh@glassegg.com> wrote in message > news:1112941264.015260.288950@f14g2000cwb.googlegroups.com... >> hi all, >> >> Our app got a long-term headache bug, that is our App sometimes quit >> unexpectedly without any warning. We heard that if installing SP3, >> everything is OK. But that's not true. Even installing SP3, our app >> still quit. >> We use a tool for automatically test 1 event load form, and write to >> log file to check in detail. The test report is as follows: >> >> 1) Hardware >> PDA Client machine: Pocket Loox/ FLX3AW >> CPU: Intel PXA 255 400MHz >> Memory: RAM 128M and ROM 64 M >> OS: Window Mobile 2003 software for Pocket PC >> Database: MS SQL CE >> >> 2) Software >> Test: Pocket PC Controller Professional Version 4.12 >> Delopement: VB.NET compact framework >> >> 3) Metrics >> Total number tests: 250 >> Total number of quiting unexpectedly: 18 >> Test place: event load form of a specific form >> >> 4) Average Memory(GlobalStatusMemory API function) >> >> MemoryLoad: 46 >> TotalPhysical: 51.859375 >> AvailablePhysical: 28.21875 >> TotalPageFile: 0 >> AvailPageFile: 0 >> TotalVirtual: 32 >> AvailVirtual: 22.4375 >> >> >> 5) Result >> It quit in any place in load form event, even at the end of >> function Load_Form >> >> We think of 4 capabilities: >> >> - Our App has a serious bug ? >> - Memory isn't enough ? >> - Window Mobile 2003 has a problem ? >> - Pocket PC Fujitsu device has a problem >> >> >> Any help to light up for us? >> Thanks, >> KNC >> > >
Depends on usage. You can catch some exceptions with P/Invokes (like
MissingMethodException). In other cases you have to be careful with parameters. Keep in mind that even the Microsoft pieces of the CF contain a *lot* of P/Invokes, since that's how you call native APIs. So while you think you've "replaced all the P/Invoke calls" you've likely just move the location of the P/Invoke out of your own code, but it's still happening. Unexpected shutdowns with no warning or error are usually due to a low-memory condition and the PPC shuts you down. -Chris [quoted text, click to view] "McFar" <_NO_NO__REMOVE_@6784.com> wrote in message news:eFxIUlCPFHA.3292@TK2MSFTNGP12.phx.gbl... >I am not sure that exception handling will help here.... > I posted an example of simple application here a couple of weeks ago, that > does nothing just PInvokes huge number of times in a row > and the application just disappeared, none exception, none message, just > disappeared.... > So I supposed that it is a PInvoke problem and replaced all the PInvoke > calls onto managed > functions, the application works fine now... > > "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message > news:OQAK9PCPFHA.2736@TK2MSFTNGP09.phx.gbl... >> Or use exception handling. There's no reason top avoid P/Invokes just >> becasue you fear them. >> >> -Chris >> >> >> >> "McFar" <_NO_NO__REMOVE_@6784.com> wrote in message >> news:uStfM$APFHA.2468@tk2msftngp13.phx.gbl... >> > Hello, I have the same problem and found a ay to fix it, in my > application >> > it was because of >> > PInvoke to native functions. :) >> > >> > Does your application PInvoke to native functions? If does, so try to > find >> > out another solution to avoid PInvoke >> > >> > >> > "KNC" <khanh@glassegg.com> wrote in message >> > news:1112941264.015260.288950@f14g2000cwb.googlegroups.com... >> >> hi all, >> >> >> >> Our app got a long-term headache bug, that is our App sometimes quit >> >> unexpectedly without any warning. We heard that if installing SP3, >> >> everything is OK. But that's not true. Even installing SP3, our app >> >> still quit. >> >> We use a tool for automatically test 1 event load form, and write to >> >> log file to check in detail. The test report is as follows: >> >> >> >> 1) Hardware >> >> PDA Client machine: Pocket Loox/ FLX3AW >> >> CPU: Intel PXA 255 400MHz >> >> Memory: RAM 128M and ROM 64 M >> >> OS: Window Mobile 2003 software for Pocket PC >> >> Database: MS SQL CE >> >> >> >> 2) Software >> >> Test: Pocket PC Controller Professional Version 4.12 >> >> Delopement: VB.NET compact framework >> >> >> >> 3) Metrics >> >> Total number tests: 250 >> >> Total number of quiting unexpectedly: 18 >> >> Test place: event load form of a specific form >> >> >> >> 4) Average Memory(GlobalStatusMemory API function) >> >> >> >> MemoryLoad: 46 >> >> TotalPhysical: 51.859375 >> >> AvailablePhysical: 28.21875 >> >> TotalPageFile: 0 >> >> AvailPageFile: 0 >> >> TotalVirtual: 32 >> >> AvailVirtual: 22.4375 >> >> >> >> >> >> 5) Result >> >> It quit in any place in load form event, even at the end of >> >> function Load_Form >> >> >> >> We think of 4 capabilities: >> >> >> >> - Our App has a serious bug ? >> >> - Memory isn't enough ? >> >> - Window Mobile 2003 has a problem ? >> >> - Pocket PC Fujitsu device has a problem >> >> >> >> >> >> Any help to light up for us? >> >> Thanks, >> >> KNC >> >> >> > >> > >> >> > >
Hi all,
First of all, thanks for your all reply. Regarding P/Invokes, we use a lof of this feature in our app and that's OK. The event load form of our test form has no P/Invokes at all. For "low-memory condition and the PPC shuts you down", I heard much about this and you can see the memory report, the available virtual memory is 22 MBs approximately, so that can not be this case. Moreover, our app even quit suddenly once just launch it. Any help would be very appreciated, Kindly regards, KNC
[quoted text, click to view]
>>There are a couple of possible reasons why your app may die under >>continuous P/Invoking, perhaps your P/Invoke definitions are wrong, >>perhaps you are not correctly handling an error condition, I used to reproduce the problem using different API here is another new way to play hide and seek. private void button1_Click(object sender, System.EventArgs e) { try { OpenNETCF.Win32.RegistryKey reg = OpenNETCF.Win32.Registry.ClassesRoot; int i = 0; while(i < 500) { string[] keys = reg.GetSubKeyNames(); i++; keys = null; } } catch(Exception eh) { MessageBox.Show(eh.Message); } } Be patient and u get an apple :) It fails occasionally, but it will.... Once, it was long ago, I got this error message ExceptionCode: 0x80000002 ExceptionAddress: 0x0159FEC0 But it was only once. So having all this happiness, I removed all PInvoke from my application. [quoted text, click to view] "Peter Foot [MVP]" <feedback@nospam-inthehand.com> wrote in message news:e4AMJvCPFHA.3908@TK2MSFTNGP10.phx.gbl... > If the function you are P/Invoking has a direct managed equivalent then of > course you should use that instead, but especially with the Compact > Framework there are times when you need to use P/Invoke because the > functionality is not included in the standard class libraries.Do not > forget that at some point all of the managed classes are calling down to > the underlying OS for their functionality. > There are a couple of possible reasons why your app may die under > continuous P/Invoking, perhaps your P/Invoke definitions are wrong, > perhaps you are not correctly handling an error condition, or perhaps you > are not correctly allocating or freeing native memory. If you can pinpoint > a specific function then post your P/Invoke declaration and code snippet > of it in use and we can advise further. > > Peter > > -- > Peter Foot > Windows Embedded MVP > http://www.inthehand.com | http://blog.opennetcf.org/pfoot/ > > "McFar" <_NO_NO__REMOVE_@6784.com> wrote in message > news:eFxIUlCPFHA.3292@TK2MSFTNGP12.phx.gbl... >>I am not sure that exception handling will help here.... >> I posted an example of simple application here a couple of weeks ago, >> that >> does nothing just PInvokes huge number of times in a row >> and the application just disappeared, none exception, none message, just >> disappeared.... >> So I supposed that it is a PInvoke problem and replaced all the PInvoke >> calls onto managed >> functions, the application works fine now... >> >> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >> news:OQAK9PCPFHA.2736@TK2MSFTNGP09.phx.gbl... >>> Or use exception handling. There's no reason top avoid P/Invokes just >>> becasue you fear them. >>> >>> -Chris >>> >>> >>> >>> "McFar" <_NO_NO__REMOVE_@6784.com> wrote in message >>> news:uStfM$APFHA.2468@tk2msftngp13.phx.gbl... >>> > Hello, I have the same problem and found a ay to fix it, in my >> application >>> > it was because of >>> > PInvoke to native functions. :) >>> > >>> > Does your application PInvoke to native functions? If does, so try to >> find >>> > out another solution to avoid PInvoke >>> > >>> > >>> > "KNC" <khanh@glassegg.com> wrote in message >>> > news:1112941264.015260.288950@f14g2000cwb.googlegroups.com... >>> >> hi all, >>> >> >>> >> Our app got a long-term headache bug, that is our App sometimes >>> >> quit >>> >> unexpectedly without any warning. We heard that if installing SP3, >>> >> everything is OK. But that's not true. Even installing SP3, our app >>> >> still quit. >>> >> We use a tool for automatically test 1 event load form, and write >>> >> to >>> >> log file to check in detail. The test report is as follows: >>> >> >>> >> 1) Hardware >>> >> PDA Client machine: Pocket Loox/ FLX3AW >>> >> CPU: Intel PXA 255 400MHz >>> >> Memory: RAM 128M and ROM 64 M >>> >> OS: Window Mobile 2003 software for Pocket PC >>> >> Database: MS SQL CE >>> >> >>> >> 2) Software >>> >> Test: Pocket PC Controller Professional Version 4.12 >>> >> Delopement: VB.NET compact framework >>> >> >>> >> 3) Metrics >>> >> Total number tests: 250 >>> >> Total number of quiting unexpectedly: 18 >>> >> Test place: event load form of a specific form >>> >> >>> >> 4) Average Memory(GlobalStatusMemory API function) >>> >> >>> >> MemoryLoad: 46 >>> >> TotalPhysical: 51.859375 >>> >> AvailablePhysical: 28.21875 >>> >> TotalPageFile: 0 >>> >> AvailPageFile: 0 >>> >> TotalVirtual: 32 >>> >> AvailVirtual: 22.4375 >>> >> >>> >> >>> >> 5) Result >>> >> It quit in any place in load form event, even at the end of >>> >> function Load_Form >>> >> >>> >> We think of 4 capabilities: >>> >> >>> >> - Our App has a serious bug ? >>> >> - Memory isn't enough ? >>> >> - Window Mobile 2003 has a problem ? >>> >> - Pocket PC Fujitsu device has a problem >>> >> >>> >> >>> >> Any help to light up for us? >>> >> Thanks, >>> >> KNC >>> >> >>> > >>> > >>> >>> >> >> > >
Again, available memory is a misnomer ic CE. You could have 100 MB "free"
and stuill run out of vitual space for your process. This is actually fairly common on newer PPC devices that load all kinds of vendor stuff (apps, utilites, etc) at boot. For a good explanation, Google "Boling CE advanced memory" and read the resulting MSDN article. -Chris [quoted text, click to view] "KNC" <khanh@glassegg.com> wrote in message news:1113018470.430716.131090@o13g2000cwo.googlegroups.com... > Hi all, > > First of all, thanks for your all reply. > Regarding P/Invokes, we use a lof of this feature in our app and that's > OK. The event load form of our test form has no P/Invokes at all. > For "low-memory condition and the PPC shuts you down", I heard much > about this and you can see the memory report, the available virtual > memory is 22 MBs approximately, so that can not be this case. Moreover, > our app even quit suddenly once just launch it. > > Any help would be very appreciated, > Kindly regards, > > KNC >
Hi Chris,
As I talked beforehand, the available virtual memory is 22 MBs approximately, so the problem "You could have 100 MB "free" and stuill run out of vitual space for your process" can not be the case. I assume that I also have knowledge about PPC memory via famous articles from Douglas Boling. Could you tell me another reasonable manner? Thanks, KNC
Again, you do not understand CE memory management. You *can* have a device
report 100MB free and still have an app run out of memory. Read this article: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncenet/html/advmemmgmt.asp -Chris [quoted text, click to view] "KNC" <khanh@glassegg.com> wrote in message news:1114058161.769220.3750@l41g2000cwc.googlegroups.com... > Hi Chris, > > As I talked beforehand, the available virtual memory is 22 MBs > approximately, so the problem "You could have 100 MB "free" and stuill > run out of vitual space for your process" can not be the case. I assume > that I also have knowledge about PPC memory via famous articles from > Douglas Boling. > Could you tell me another reasonable manner? > > Thanks, > KNC >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |