>>However, since last night, it started freezing on that line, with a "Fatal error: Exception code=C0000005" in the log, pointing to one of those behind-the-scenes calls. I guess these only add to the memory leak problem until it gets too much. What's worrying is that this used to work flawlessly for two whole nights...
>>Perhaps unrelated: In the app's log I've found that it did lots of .png files from skype snapshots, and I had some trouble initially with those. I regularly convert those to jpgs (as the compression is about 9 times better with no visible loss), but didn't do that from the start, and then there are also screenshots which better remain .png as better suited for the format.
>>
>>Is there any function to call to garbagecollect this, or a way to flush the buffers and whatever iPicture uses? Or should I be better off using plain fox-native image objects?
>
>You could try CLEAR RESOURCES. I don't know if VFPX LOADPICTURE() will respond to that, though.

Tried, that, no dice. sys(1104) helped a bit but not much. Tried Sys(3098), made it worse - caused errors or even faster leaking.

I'll probably have to go back to the good old image object.