Ribbonbar getting black

[vilian]

Hi guys,
I'm having a problem with my customers who use Windows 7. The Ribbon Bar is getting black (look the image bellow) do youknow why ?

[James Bott]

Possibly a memory leak. I have seen things like this before.

If you exit the program, then reload it, does the problem go away?

James

[vilian]

Yes, you are right!
However, it's happening only with Windows 7 users. What could I do to prevent this?

[Antonio Linares]

Vilian,

Please use FWH function SetResDebug() as explained here:

http://wiki.fivetechsoft.com/doku.php?id=fivewin_function_setresdebug

[James Bott]

Vilian,

The way you fix it is to find all unreleased objects and end them. Use the method the Antonio provided a link to.

I don't know why it is only happening on Windows 7. Maybe those pc's have less memory, or there is a bug in Win 7 itself. Either way you still need to end all the resources.

[vilian]

Thank you James,
I'm testing...

[vilian]

I don't understand... I made this:

Code: Select all  Expand view  RUN

   SetResDebug( .T. )
         ....
        My Code
        .....
   FErase( "chekres.txt" )
   CheckRes()
   WinExec( "notepad checkres.txt" )    
 

But everything shown is only this:

Code: Select all  Expand view  RUN

30/08/2018 09:45:51: C:\VFATEC\SFPDES\SFP.EXE -- ===================================================================================

[James Bott]

Vilian,

Well that is a good sign. However, you can't just open the app, then close it to find resource leaks (if that is what you did). You have to give the software a real-world workout, trying all the screens and functions to really see if there is an issue. Best would be if you can run it under Windows 7 and get the toolbar to turn black--then you know you have done enough to find the leak.

James

[vilian]

James,

I only closed the app after ribbon bar started to get black.

[James Bott]

I am away from my computer right now. When I get back I have a few things I want to look up. I'll let you know.

[James Bott]

Vilian,

OK, I ran a test program just to make sure that checkRes() is working.

Code: Select all  Expand view  RUN

#include "fivewin.ch"

Function Main()
   local oDlg, oFont
   setResDebug(.t.)
   ferase("checkres.txt")
   define font oFont name "Arial" size 0,-10
   define dialog oDlg
   activate dialog oDlg
   //oFont:end()  // don't destroy oFont for test
   checkres()
return nil
 

And here is the result.

08/30/18 14:16:00: C:\Users\James\Documents\Projects\CheckRes\TestCheckRes.exe -- FONT,-1056306525,MAIN(20)

As you can see, the font is reported as being unreleased.

I am using a fairly old copy of FWH (16.04) so you should run the test program above to make sure it also detects the unreleased font with your version of FWH.

If checkRes() seems to be working, then I would suggest running the Windows Task Manager and watching the memory as you test the program. Record the memory used when the program is first started, then run it until the toolbar turns black and record the memory use again. You could also watch what happens when you are using the app to see if the memory used goes up on certain processes.

That should keep you busy for awhile.

James

[cnavarro]

Indeed, the first thing is to use the technique indicated previously by Antonio
In addition, you can use this tool

https://www.nirsoft.net/utils/gdi_handles.html

[vilian]

James,
I really have so much care with resources and good practises, as a result checkres() is returning an empty string. I will try the tool recommend by Cnavarro.

[James Bott]

Vilian,

Any updates? Did you find a solution?

[vilian]

Hi James,

Nothing yet. Checkres() Always is returning na empty string, so by this way i didn't find a solution.