Linked by kragil on Wed 23rd Jan 2013 20:26 UTC
Thread beginning with comment 550454
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
Linked by Thom Holwerda on 04/14/13 18:22 UTC, submitted by MOS6510
More Features »
Sponsored Links



Member since:
2006-05-30
I remember a co-worker driving himself insane with CF1.0 and SqlClient. Somewhere is wasn't releasing memory correctly and basically using up all the free memory on the device. In the end, he put a number of explicit GC.Collect()'s in the code. It was a documented bug, I think it was fixed in CF2.0, but we had to use 1.0 because the devices being used didn't support 2.0 (IIRC, they were mixed, some were running PocketPC 2000 or something like that... plus most had bugger all RAM.)