G
Guest
Hi all,
I did a few search in the Google Groups archives and did not find anything
similar, hopefully I didn't miss anything and this is not redundant
(otherwise, a pointer to the right thread is appreciated.
)
I have a .NET CF application running on a Panasonic CF-P1 (rugged handheld),
running Windows Mobile 2003 with .NET CF SP3 (SP1 in is ROM, I applied SP3
myself.) I've distributed the application to a couple of colleagues in
charge of testing, and we've run into a strange -unfortunately random-
problem. Sometimes, the application stops responding. No matter where we
tap on the screen, it doesn't respond (note that I removed the Start menu
icon using that fullscreen API call, because we don't want the users to go
play in there.) At first I thought it was a complete lockup and just soft
reset the machine, but yesterday afternoon I just let it be for maybe 2
minutes, and suddenly it started responding again(!)
This SEEMS to happen when we click anywhere on the screen (there's a
datagrid there, with a couple of menus), resize the datagrid a few times,
etc... You know, "killing time" type of stuff. As I mentionned however, it
is kind of random and doesn't happen all the time. I think it has also
happened in other screens, but my testers don't always come back to me with
that kind of feedback (yeah I know, time do bust some kneecaps-lol.)
Anyway, considering the fact that it came back by itself, I was wondering if
this could be the garbage collector getting very busy or something? That
would be bad, as I'd expect it to do its cleanup in the background and not
interfere too much - or at least not for that long. But then again maybe
it's something else. I don't think it's some kind of memory leak either, as
this can happen at the very beginning on the first screen, where allocation
is done once and properly, as far as I can tell. Incidentally this is way
too large for me to post sample code (there's a Sybase database involved,
among other things.)
Sooo... In conclusion, I was wondering if anyone has run into a similar
problem, and if there are known solutions or known workarounds?
thanks,
Michel
I did a few search in the Google Groups archives and did not find anything
similar, hopefully I didn't miss anything and this is not redundant
(otherwise, a pointer to the right thread is appreciated.
)I have a .NET CF application running on a Panasonic CF-P1 (rugged handheld),
running Windows Mobile 2003 with .NET CF SP3 (SP1 in is ROM, I applied SP3
myself.) I've distributed the application to a couple of colleagues in
charge of testing, and we've run into a strange -unfortunately random-
problem. Sometimes, the application stops responding. No matter where we
tap on the screen, it doesn't respond (note that I removed the Start menu
icon using that fullscreen API call, because we don't want the users to go
play in there.) At first I thought it was a complete lockup and just soft
reset the machine, but yesterday afternoon I just let it be for maybe 2
minutes, and suddenly it started responding again(!)
This SEEMS to happen when we click anywhere on the screen (there's a
datagrid there, with a couple of menus), resize the datagrid a few times,
etc... You know, "killing time" type of stuff. As I mentionned however, it
is kind of random and doesn't happen all the time. I think it has also
happened in other screens, but my testers don't always come back to me with
that kind of feedback (yeah I know, time do bust some kneecaps-lol.)
Anyway, considering the fact that it came back by itself, I was wondering if
this could be the garbage collector getting very busy or something? That
would be bad, as I'd expect it to do its cleanup in the background and not
interfere too much - or at least not for that long. But then again maybe
it's something else. I don't think it's some kind of memory leak either, as
this can happen at the very beginning on the first screen, where allocation
is done once and properly, as far as I can tell. Incidentally this is way
too large for me to post sample code (there's a Sybase database involved,
among other things.)
Sooo... In conclusion, I was wondering if anyone has run into a similar
problem, and if there are known solutions or known workarounds?
thanks,
Michel