3dify crashes after scanning

[Moe]

Hello!  First of all I am super excited about the progress you guys have made and I expect this to be a top-dog application before it is all said and done.  So thank you for your hard work and for making this available. 
 Now.  My issue is a consistent crashing after the scan and processing of the images.  After the point where it asks what areas to exclude I choose ok and it crashes immediately.  I am running on a Win7 64 desktop with 2GB DRAM and an Nvidia GeForce 8400GS PCIe graphics card with either 256 or 512MB of its own ram.  Processor is a Pentium D 2.8GHz.  Three other machines with onboard graphics cards and lesser processors all failed to see the kinect with any regularity and when they did 3dify would crash during the imaging phase within a few seconds.  These older machines were a mix of XP and Vista and 7 32 bit and probably not representative of the machines and configurations you will most likely have to support ( I assume).
   I include the logfile from my latest crash on the Win7 64 bit, Pentium D 2.8 GHz, 2GB Dram, GeForce 8400GS machine.  Again, thanks for making this wonderful software available to us.
                                                                                                                                                                                                                         Cheers,
                                                                                                                                                                                                                               Moe
PS.  I will be trying this on my daughter's souped-up gaming computer to see if raw horsepower makes a difference.

[Moe]

Also I moved the interval up to anywhere from 17 to 20 with the same result.

[Chytu]

Can you try the following and see if the crash appears again:

• Start a new Meshing project
• Select the "temp_<projectName>.pcd" file that has been generated before crash

If the crash does not occur this time, then the earlier crash is a known issue that we are currently working on fixing.

Thanks,

Chytu.