Flare 3.1 stays in memory after closing

This forum is for all Flare issues related to using Source Control.

Flare 3.1 stays in memory after closing

Postby 7man40 on Sat Jan 03, 2009 12:21 am

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
7man40
Propeller Head
 
Posts: 27
Joined: Tue Dec 23, 2008 9:53 pm

Re: Flare 3.1 stays in memory after closing

Postby helen on Mon Jan 05, 2009 12:42 am

FYI

viewtopic.php?f=13&t=3501
viewtopic.php?f=13&t=3969

I don't know if there's a fix - I've not tried to bind it again.
helen
Sr. Propeller Head
 
Posts: 276
Joined: Thu Oct 25, 2007 5:57 am
Location: Manchester, UK

Re: Flare 3.1 stays in memory after closing

Postby 7man40 on Mon Jan 05, 2009 8:28 pm

Thanks a lot for the info helen. I will post any info I learn on Perforce and Flare.
7man40
Propeller Head
 
Posts: 27
Joined: Tue Dec 23, 2008 9:53 pm


Return to Source Control

Who is online

Users browsing this forum: No registered users and 2 guests