Memory "Leak" uppon calling GUICtrlSetImage

[careca]

Hi everyone! I noticed that on my compiled script the used memory increases a few KB everytime i call:

GUICtrlSetImage($ButtonXYZ, @ScriptDir & "\somebmp.bmp")

Makes sense, since im basically pasting image uppon image onto the button, at least this is how i understand it.

Question is: What do you recommend? Using a different function to do the same, or some code to somehow clear the previous images? or what?

Best regards.

[BrewManNH]

Good question, show your code and you might get an answer.

[guinness]

Look at Resources Ex UDF, which contains GUICtrlSetMsg(). Find that and you will get your answer of destroying an image.

[careca]

@Brewmanh: Code is right there, an MVP like you shouldn't need more than that to provide a pointer in the right direction.

Thanks guinness, You answered the question about deleting the resources, meanwhile my thought has shifted and i was wondering if it wouldn't be more efficient to load the image to memory, only once, into a variable, and then use the variable when needed, think this can be possible? There's even GDI+ that i already use in other stuff.

Best regards.

[BrewManNH]

@Brewmanh: Code is right there, an MVP like you shouldn't need more than that to provide a pointer in the right direction..

If that one line of code was enough, do you think I would have asked to see your script?

It could be that it has nothing to do with the line you posted and the problem lies elsewhere, but we'll never know because you only posted one line, that only you seem to be having an issue with.

[careca]

OK, if you think it really makes a difference.

expandcollapse popup

#Region ;Wrapper
#pragma compile(UPX, false)
#AutoIt3Wrapper_UseUpx=n
#AutoIt3Wrapper_UseX64=n
#AutoIt3Wrapper_Run_Tidy=y
#AutoIt3Wrapper_Res_SaveSource=y
#AutoIt3Wrapper_Res_Fileversion=1.0
#AutoIt3Wrapper_AU3Check_Parameters=-d -w 1 -w 2 -w 3 -w- 4 -w 5 -w 6 -w- 7
#EndRegion ;Wrapper
;=============================================================================
#Region ;FileInstall
;FileInstall("file", @ScriptDir & "\file")
#EndRegion ;FileInstall
;=============================================================================
#Region
#include <GUIConstants.au3>
#include <TrayConstants.au3>
#include <GUIConstantsEx.au3>
#include <WindowsConstants.au3>
#EndRegion
;=============================================================================
#Region
OnAutoItExitRegister("Quit")
#EndRegion
;=============================================================================
#Region
Global $GUI

$GUI = GUICreate("Test Window", 180, 75, 0, 0)
GUISetState()
TraySetState(1)
TraySetClick(16)
$WinState = 1

GUISetOnEvent($GUI_EVENT_CLOSE, "Quit")
Local $Button = GUICtrlCreatePic(@ScriptDir & "\test.bmp", 10, 10, 40, 40)
GUICtrlSetOnEvent($Button, "Button")

$exititem = TrayCreateItem("Close")
TrayItemSetOnEvent(-1, "Quit")
#EndRegion
;=============================================================================
Func Button()
    GUICtrlSetImage($Button, @ScriptDir & "\test.bmp")
EndFunc   ;==>Button
;=============================================================================
Func Quit()
    Exit
EndFunc   ;==>Quit
;=============================================================================
Do
sleep(100)
Until GUIGetMsg() = $GUI_EVENT_CLOSE

Each press of the button increases memory use, in the more complex script, a certain function will change the image, and another function changes the button to a different image, so the button changes as needed.

Best regards

Edited December 14, 2015 by careca
Clarification

[BrewManNH]

That script doesn't even work as you wrote it, you're using OnEvent mode and messageloop mode in the same script. So, when you run that script the button never gets fired.

I changed that so it at least works as intended, and I do not see any increase in memory usage whatsoever, even pressing the button 100 times does nothing to the memory usage. It always shows exactly the same amount of memory used.

[careca]

Yes, you're correct, i forgot to include Opt("GUIOnEventMode", 1), and i tested the script, and as you said, the memory didn't increase, so i adapted it a bit, could you test this one please?

expandcollapse popup

#Region ;Wrapper
#pragma compile(UPX, false)
#AutoIt3Wrapper_UseUpx=n
#AutoIt3Wrapper_UseX64=n
#AutoIt3Wrapper_Run_Tidy=y
#AutoIt3Wrapper_Res_SaveSource=y
#AutoIt3Wrapper_Res_Fileversion=1.0
#AutoIt3Wrapper_AU3Check_Parameters=-d -w 1 -w 2 -w 3 -w- 4 -w 5 -w 6 -w- 7
#EndRegion ;Wrapper
;=============================================================================
#Region ;FileInstall
;FileInstall("file", @ScriptDir & "\file")
#EndRegion ;FileInstall
;=============================================================================
#Region
#include <GUIConstants.au3>
#include <TrayConstants.au3>
#include <GUIConstantsEx.au3>
#include <WindowsConstants.au3>
#EndRegion
;=============================================================================
#Region
Opt("GUIOnEventMode", 1)
OnAutoItExitRegister("Quit")
#EndRegion
;=============================================================================
#Region
Global $GUI

$GUI = GUICreate("Test Window", 180, 75, 0, 0)
GUISetState()
TraySetState(1)
TraySetClick(16)

GUISetOnEvent($GUI_EVENT_CLOSE, "Quit")
Local $Button = GUICtrlCreatePic(@ScriptDir & "\test.jpg", 10, 10, 40, 40)
GUICtrlSetOnEvent($Button, "Button")

Local $exititem = TrayCreateItem("Close")
TrayItemSetOnEvent(-1, "Quit")
#EndRegion
;=============================================================================
Func Button()
    ConsoleWrite('click ' & @CRLF)
    GUICtrlSetImage($Button, @ScriptDir & "\test.bmp")
    Sleep(300)
    GUICtrlSetImage($Button, @ScriptDir & "\test.jpg")
EndFunc   ;==>Button
;=============================================================================
Func Quit()
    Exit
EndFunc   ;==>Quit
;=============================================================================

Do
    Sleep(100)
Until GUIGetMsg() = $GUI_EVENT_CLOSE

This one should represent what i mean.

test.bmp