SCI Seg3D Mailing List

Text archives Help


[Seg3D] RE: Re: seg 3d memory issues


Chronological Thread 
  • From: "Barbir,Ana" <Ana.Barbir@ColoState.EDU>
  • To: "seg3d@sci.utah.edu" <seg3d@sci.utah.edu>
  • Subject: [Seg3D] RE: Re: seg 3d memory issues
  • Date: Thu, 28 Jun 2012 16:21:38 +0000
  • Accept-language: en-US
Hi Jeroen, thanks for the tip. I just tried that.
With the undo buffer unchecked, it seems to do it when I am using other tools too. It started climbing in memory even if I just scroll through my image stack or use the confidence connected filter. These tasks made it get up to 1G, but as soon as I started using paint brush, it climbed all the way to 6.9G. Once it reaches that number, it seemed to stay there longer without crashing than it normally does (although everything was very slow). When it finally crashed, I did not get the windows warning, and it went down to about 150M on its own. However, unlike before, the first crash did not fix the problem, and as soon as I started using any tools, it started climbing back up in memory and being noticeably slower.
Ana


______________________________________
Ana Barbir
Postdoctoral Researcher
Orthopaedic Research Center
College of Veterinary Medicine and Biomedical Sciences
Colorado State University
Fort Collins, CO

From: Jeroen Stinstra [jeroen@sci.utah.edu]
Sent: Wednesday, June 27, 2012 6:47 PM
To: seg3d@sci.utah.edu
Subject: [Seg3D] Re: seg 3d memory issues

Hi Ana,

I think the problem is that it miscalculated the number of available memory it can use. It has been designed to use up to roughly 50% of memory for undo buffering (it is configurable in the Preferences). The first thing to check is to switch off the undo buffer in the Preferences, that will help pinpoint the problem.

If that is the problem it should be easy to fix.

Jeroen



On Jun 27, 2012, at 3:18 PM, Barbir,Ana wrote:

Hello,
I was hoping someone might have some insight into this issue. A few month ago I downloaded Seg 3D (the newest version, 2.1.4) and when I start using most tools, it works fine (memory usage around 140M). However as soon as I start using the paint brush tool, the memory usage goes above 1G, and as I keep using it, it just keeps increasing, eventually going up to 7G at which point windows tells me to close the application. I use Windows 7 64 bit (8GB RAM) and when I installed it it was a brand new machine.

This is not an isolated incident, this happens every time I use it. I have tried installing version 2.1.1. since that is what our collaborators use without any issues (on the same data sets) but it still does the same thing. The only trick I have discovered is to not close it when it reaches 7M and gives me the warning. It then slowly goes down to a normal value of ~140M, and I can from that point use paintbrush tool on any files I like without problem. The only annoying this is that every time I restart the system, I have to go through this whole long process, wait for it to crash, wait for the memory to reach normal levels and then start working.  

I have also tried just waiting for the memory usage to go down before the warning, but it does not, and it becomes pretty slow to use. Any suggestions would be appreciated.
Ana

______________________________________
Ana Barbir
Postdoctoral Researcher 
Orthopaedic Research Center
College of Veterinary Medicine and Biomedical Sciences
Colorado State University
Fort Collins, CO



Archive powered by MHonArc 2.6.16.

Top of page