Jump to content
Sign in to follow this  
ChrisL

Memory Leak with Flash

Recommended Posts

I have a memory leak caused by an object ShockwaveFlash.

The below script will delete the the control and the object and recreate it, if you watch the memory in Task Manager it keeps going up every time you delete and recreate the control.

Any ideas?

Thanks

 

 
Opt("GuiOnEventMode",1)

#include <GUIConstantsEx.au3>
Global $hGui, $flashControl, $SWFObj

_Gui()

While 1
Sleep(250)
WEnd

Func _Gui()

$hGui = GUICreate("ShockwaveFlash.ShockwaveFlash",280,280)
GuiSetState()
GUISetOnEvent($GUI_EVENT_CLOSE,"_Exit")

$flashControl = _CreateSWF(@scriptDir & "\loading9.swf", 40,40, 200,200)

Local $button = GUICtrlCreateButton("Delete and Renew",10,10)
GUICtrlSetOnEvent($button,"_DeleteFlashControlAndCreateANewOne")

EndFunc


Func _DeleteFlashControlAndCreateANewOne()

GUICtrlDelete($flashControl)
ConsoleWrite("$SWFObj is object = " & IsObj($SWFObj) & @CRLF)
$SWFObj = 0
ConsoleWrite("$SWFObj is object = " & IsObj($SWFObj) & " so why don't I get my memory back?" & @CRLF)
Sleep(250)
$flashControl = _CreateSWF(@scriptDir & "\loading9.swf", 40,40, 200,200)

EndFunc

Func _CreateSWF($SWFPath, $SWFL, $SWFT, $SWFW, $SWFH, $SWFBGColor = "#000000")

If NOT FileExists($SWFPath) then Return

$SWFObj = ObjCreate("ShockwaveFlash.ShockwaveFlash")
Local $SWFActiveX = GUICtrlCreateObj($SWFObj, $SWFL, $SWFT, $SWFW, $SWFH)

With $SWFObj
.Movie = $SWFPath
.ScaleMode = 1
.bgcolor = $SWFBGColor
.Loop = True
.allowScriptAccess = "Always"
.Quality = 1
.Playing = 1
.Menu = 1
EndWith

Return $SWFActiveX

EndFunc

Func _Exit()
Exit
EndFunc

 

loading9.zip

Share this post


Link to post
Share on other sites

I've seen this issue raised before, I don't think there was a solution if I recall.

Let me ask, id this a real world problem for you or are you just showcasing that you think you found a bug?

Can you demonstrate the real world issue if it is that?

Share this post


Link to post
Share on other sites

Or perhaps add a long sleep duration between deleting and creating the object, I had the same issue with _IENavigate (irrelevant I know) where _IEQuit didn't work everytime and the process would start hugging the memory and causing a leak.

Share this post


Link to post
Share on other sites

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...