I moved this from the "Flare's General Discussion" forum after it narrowed down to a source control problem (hope that's okay). Here's what happens:
I open Flare, then open a project that is bound to source control. CPU utilization of Flare.exe process in Task Manager at this point: 0% or so.
Then I close Flare. But the Flare.exe process remains in Task Manager, and within 5 seconds the CPU goes over 90% on the Flare.exe process and pretty much stays there. No error messages or anything. Tends to turn on the fan on my laptop. I have to close the Flare.exe process in Task Manager.
This does not happen if I have opened a project that is not bound to source control. I am using Perforce through the SCC API. My Perforce server is available and I can check out and check in files.
helen in Flare's General Discussion forum said she had reported this as a bug. I'm wondering if there has been any fix for it.
Thanks
Flare 3.1 stays in memory after closing
Re: Flare 3.1 stays in memory after closing
FYI
http://forums.madcapsoftware.com/viewto ... =13&t=3501
http://forums.madcapsoftware.com/viewto ... =13&t=3969
I don't know if there's a fix - I've not tried to bind it again.
http://forums.madcapsoftware.com/viewto ... =13&t=3501
http://forums.madcapsoftware.com/viewto ... =13&t=3969
I don't know if there's a fix - I've not tried to bind it again.
Re: Flare 3.1 stays in memory after closing
Thanks a lot for the info helen. I will post any info I learn on Perforce and Flare.