News:

 

Topic: Crash when decreasing subdivision level  (Read 6067 times)

0 Members and 1 Guest are viewing this topic.

  • No avatar
  • Posts: 976
  • Polygon
April 12, 2013, 01:10:10 pm
NVil crashes on me when I try to decrease subdivision by one step.
Model has 7.3k polys. I use subdivision level 3 (~469k) to inspect its smoothness. When I try to decrease subdivision to level 2, program either crashes or gets lost by displaying wrong poly counts (e.g. ~350k instead of ~118k for subdivision 2). Sometimes it manages to return to subdiv 2 without crashing.

It appears it's running out of memory.
Code: [Select]
  Problem Event Name: CLR20r3
  Problem Signature 01: nvil 1.0.exe
  Problem Signature 02: 2.3.4850.332
  Problem Signature 03: 51669a48
  Problem Signature 04: WorkShop
  Problem Signature 05: 2.3.4850.324
  Problem Signature 06: 51669a39
  Problem Signature 07: 1d9a
  Problem Signature 08: 3b8
  Problem Signature 09: System.OutOfMemoryException
  OS Version: 6.1.7601.2.1.0.256.48
And I'm not sure why, because at subdiv 3 it uses 1.2GB of RAM, so there's still some RAM left for it to use before reaching its limit of 2GB (or is it 3GB for 32-bit processes?). The peak of RAM usage by NVil is 1.3GB. I've never seen it use more, even right before the crash.
Also, if it doesn't crash at subdiv 3, why does it crash when I lower it to 2?

  • No avatar
  • Posts: 2103
  • Polygon
April 12, 2013, 01:29:15 pm
Hi rubberDuck,

A 32 bit application, by default, will only be able to use approx 1.3GB of ram.

If you are using 64bit OS with enough memory (or 32bit system with 4GB), you can use LAA(Large Address Aware) to increase memory NVIL can use from the 1.3 to approx 3.5

There is an application you can use (I use it myself) http://www.techpowerup.com/forums/showthread.php?t=112556


I have just been checking. It looks like IStonia has put in place a limit to help stop running out of memory with sub-d. NVIL refuses to create more sub-d when memory limit being hit(on my setup).

The problem you are seeing, is possibly (and I am only guessing) that an "undo" is being created when reducing sub-d and taking more memory, causing issue.

« Last Edit: April 12, 2013, 01:39:39 pm by steve »

  • No avatar
  • Posts: 976
  • Polygon
April 12, 2013, 01:47:02 pm
Nice little program Steve, thanks. Looks like it solved my problem for now.
I'm curious if there any plans of moving to 64-bit architecture in the future?

P.S. Steve, it appears Inc/Dec Subdivision command can't be undone, so it's probably not stored on undo stack.
« Last Edit: April 12, 2013, 01:49:35 pm by rubberDuck »

  • No avatar
  • Posts: 2103
  • Polygon
April 12, 2013, 01:53:19 pm
I'm curious if there any plans of moving to 64-bit architecture in the future?

It is something I would like to see, and something IStonia will need to do eventually, but it would be a massive undertaking for one programmer.

Quote
P.S. Steve, it appears Inc/Dec Subdivision command can't be undone, so it's probably not stored on undo stack.
I never was good at guessing LOL.

  • No avatar
  • Posts: 976
  • Polygon
April 12, 2013, 02:05:01 pm
Yeah, I can only speculate, but this kind of migration probably isn't one of the easiest things to do. :)

Well, well this LAA application doesn't even have to be kept running in the background. Very convenient.

  • No avatar
  • Posts: 7
  • Vertex
April 15, 2013, 09:02:10 am
One of the very few weakpoints Silo had was being a 32 bit app and never got to 64 bits. Having that said, it is still the #1 modeling app out there. I really hope before the program gets to huge, the developers will focus on a 64 bits version as well. Fingers crossed.