When I close Flare 3.1, it often stays in memory and runs up the CPU to 90+%. I have waited to see if it stops, but it appears to just keep going (30 minutes plus verified). I usually end the Flare.exe process in Task Manager. Any idea what's causing this?
Thanks
Search found 27 matches
- Mon Dec 29, 2008 3:56 pm
- Forum: Flare's General Discussion
- Topic: Flare 3.1 stays in memory after closing
- Replies: 13
- Views: 5859
- Wed Dec 24, 2008 2:28 pm
- Forum: Source Control
- Topic: Anyone using a non-MS CMS to manage Flare?
- Replies: 4
- Views: 5469
Re: Anyone using a non-MS CMS to manage Flare?
I wouldn't call this a "CMS" like Vasont, but I'm using the Perforce source code control management system with Flare. The engineering department of my client already had the Perforce server set up for engineers, and they had extra licenses we are using.
I just started a few days ago and Flare ...
I just started a few days ago and Flare ...