Maybe is connected to this viewtopic.php?f=6&t=22142 ?
Update: I'm getting this problem under my XP too. I just compile and run my application and immediately see the vanishing bitmaps. So I don't think it's a resource leak problem.
EMG
Yes. I confirm it.
What's wrong?.
...
...
ACTIVATE DIALOG oDlgMain ;
ON INIT ( oDlgMain:Move( 120 , 70, 900, 265, .f. ), DLG_BAR() )
RETURN( NIL )
// ------- BUTTONBAR MAIN - DIALOG ----------------
// ---------------------------------------------------------------
FUNCTION DLG_BAR()
LOCAL oBar, oBtn1, oBtn2, oBtn3, oBtn4, oBtn5, oBtn6, oBtn7, oBtn8, oBtn9
DEFINE BUTTONBAR oBar OF oDlgMain2 SIZE 100, 55 3DLOOK 2007 TOP
...
...
Uwe,
Try to compile and start many times your app. You will see vanishing bitmaps
Hi,
Any update?
Thanks.
I even use xHarbour recently (last svn version) and never experience this error, I recently changed to harbor for testing the latest version (svn) and I are two occasions where the bitmap disappear. 
Carlos,
Thank you for your feedback.
Where you able to track it?.
tried to duplicate the error, but has not been shown again, but again with xHarbour never happened.
I'm using xHarbour and saw the problem as well.
EMG
TBar and BUTTONBAR are the same class (TBar). TBar is the class, BUTTONBAR is a command that creates an instance of TBar.
EMG
Antonio,
Any clue?.
This is very important !!!.
Thank you.
Antonio,
Can you please look at this?.
Thank you very much.
I have never seen this problem myself, anyhow I think that we have two things to check:
Check the bitmap handle before painting it to see if it still is a valid GDI object. There is a function IsGdiObject() that we can use
Painting a bitmap involves the creation of new DCs (hDC) that eventually could fail on low memory conditions, this is very difficult to happen, but we could check it.
Finally the way to go is to create a log file and check every single step taken when a bitmap is going to be painted. I am going to show how to create and implement such log file. Then. For those of you where it is failing, you will just have to review the log file and we will get a clear idea of what is happening
