Revo Scan 4.0.3.0705c periodically crashes during the fusing process. It happens approximately in 10% cases, when it reaches 63% in my case, then holds at this number for a period of time, then closes without any prompt. The pixel cloud usually still present on disk, but the consecutive fusing attempt usually produces worse results than performed during the scan. I suspect it internally generates ‘Divide by zero’ exception while fusing.
Part of the log file of such event:
2022-07-22 16:26:22.436 "https://reg.infly3d.com/device_email/user/check_sn_bound" http post data: "{\"num\":\"1\",\"data\":[{\"sn\":\"A21A0260206F00A54\",\"sv\":\"4.0.3.0705c\",\"fv\":\"v2.7.46.20220518\",\"av\":\"v7.5.6.0414\",\"date_time\":\"2022-07-22 15:00:28\"}],\"language\":\"en_US\"}"
2022-07-22 16:26:23.569 http response data: "{\"msg\":\"OK\",\"code\":200,\"data\":{\"openWindow\":0,\"url\":null}}"
2022-07-22 16:26:23.658 http response data: "{\"msg\":\"未发现新版本.\",\"data\":null,\"code\":1000}"
2022-07-22 16:26:25.077 callback<device Change>! ---- added device count: 1 ,removed device count: 0
2022-07-22 16:26:27.080 start<start camera>! ---- device status: 0
2022-07-22 16:26:27.118 success<start camera>! ---- connect Camera!
2022-07-22 16:26:27.120 success<start camera>! ---- get Camera info!
2022-07-22 16:26:27.168 Read camera file(camera path): /data/camparam/LC_RT.bin
2022-07-22 16:26:27.183 Read camera file(destination path): C:/Users/arifg/handylookdata/data/LC_RT.bin
2022-07-22 16:26:27.185 Read camera file error code = 0 ---- file size: 48
2022-07-22 16:26:27.187 Read camera file(camera path): /data/camparam/Distort.bin
2022-07-22 16:26:27.203 Read camera file(destination path): C:/Users/arifg/handylookdata/data/Distort.bin
2022-07-22 16:26:27.205 Read camera file error code = 0 ---- file size: 20
2022-07-22 16:26:27.207 Read camera file(camera path): /data/camparam/Pl.bin
2022-07-22 16:26:27.223 Read camera file(destination path): C:/Users/arifg/handylookdata/data/Pl.bin
2022-07-22 16:26:27.224 Read camera file error code = 0 ---- file size: 40
2022-07-22 16:26:27.226 Read camera file(camera path): /data/camparam/camparamLR/Q.bin
2022-07-22 16:26:27.245 Read camera file(destination path): C:/Users/arifg/handylookdata/data/Q.bin
2022-07-22 16:26:27.246 Read camera file error code = 0 ---- file size: 64
2022-07-22 16:26:27.247 Read camera file(camera path): /data/camparam/mapparamL.bin
2022-07-22 16:26:27.268 Read camera file(destination path): C:/Users/arifg/handylookdata/data/mapparamL.bin
2022-07-22 16:26:27.270 Read camera file error code = 0 ---- file size: 148
2022-07-22 16:26:27.272 Read camera file(camera path): /data/camparam/mapparamR.bin
2022-07-22 16:26:27.291 Read camera file(destination path): C:/Users/arifg/handylookdata/data/mapparamR.bin
2022-07-22 16:26:27.292 Read camera file error code = 0 ---- file size: 148
2022-07-22 16:26:27.294 Read camera file(camera path): /data/camparam/Prgb.bin
2022-07-22 16:26:27.310 Read camera file(destination path): C:/Users/arifg/handylookdata/data/Prgb.bin
2022-07-22 16:26:27.311 Read camera file error code = 0 ---- file size: 40
2022-07-22 16:26:27.314 start depth stream Info: 640 400 5 3
2022-07-22 16:26:29.321 success<start depth stream>! ---- start stream!
2022-07-22 16:26:29.346 start rgb stream Info: 1280 800 30 0
2022-07-22 16:26:29.361 success<start color stream>! ---- start stream!
2022-07-22 16:26:30.444 set frame time : 7000
2022-07-22 16:26:30.448 set default exposure : 5000
2022-07-22 16:26:30.484 set rgb auto!
2022-07-22 16:26:51.986 set accuracy mode : false
2022-07-22 16:26:52.007 set accuracy mode : false
2022-07-22 16:26:52.118 set exposure : 3000
2022-07-22 16:27:06.850 set rgb manual!
2022-07-22 16:29:55.042 fuse! ---- progress: 0
2022-07-22 16:29:56.964 fuse! ---- progress: 5
2022-07-22 16:29:57.180 fuse! ---- progress: 6
2022-07-22 16:29:57.395 fuse! ---- progress: 7
2022-07-22 16:29:57.610 fuse! ---- progress: 8
2022-07-22 16:29:57.826 fuse! ---- progress: 9
2022-07-22 16:29:58.254 fuse! ---- progress: 10
2022-07-22 16:29:58.469 fuse! ---- progress: 11
2022-07-22 16:29:58.686 fuse! ---- progress: 12
2022-07-22 16:29:58.901 fuse! ---- progress: 13
2022-07-22 16:29:59.330 fuse! ---- progress: 14
2022-07-22 16:29:59.546 fuse! ---- progress: 15
2022-07-22 16:29:59.975 fuse! ---- progress: 16
2022-07-22 16:30:00.192 fuse! ---- progress: 17
2022-07-22 16:30:00.409 fuse! ---- progress: 18
2022-07-22 16:30:00.625 fuse! ---- progress: 19
2022-07-22 16:30:01.056 fuse! ---- progress: 20
2022-07-22 16:30:01.490 fuse! ---- progress: 21
2022-07-22 16:30:01.922 fuse! ---- progress: 22
2022-07-22 16:30:13.231 fuse! ---- progress: 23
2022-07-22 16:30:13.448 fuse! ---- progress: 24
2022-07-22 16:30:13.667 fuse! ---- progress: 25
2022-07-22 16:30:15.165 fuse! ---- progress: 26
2022-07-22 16:30:18.583 fuse! ---- progress: 27
2022-07-22 16:30:18.799 fuse! ---- progress: 28
2022-07-22 16:30:20.511 fuse! ---- progress: 29
2022-07-22 16:30:21.581 fuse! ---- progress: 30
2022-07-22 16:30:21.798 fuse! ---- progress: 31
2022-07-22 16:30:22.871 fuse! ---- progress: 32
2022-07-22 16:30:23.087 fuse! ---- progress: 33
2022-07-22 16:30:23.518 fuse! ---- progress: 34
2022-07-22 16:30:23.950 fuse! ---- progress: 35
2022-07-22 16:30:24.167 fuse! ---- progress: 36
2022-07-22 16:30:25.025 fuse! ---- progress: 37
2022-07-22 16:30:25.241 fuse! ---- progress: 38
2022-07-22 16:30:29.085 fuse! ---- progress: 39
2022-07-22 16:30:29.729 fuse! ---- progress: 40
2022-07-22 16:30:29.946 fuse! ---- progress: 41
2022-07-22 16:30:34.860 fuse! ---- progress: 42
2022-07-22 16:30:38.276 fuse! ---- progress: 43
2022-07-22 16:30:39.560 fuse! ---- progress: 50
2022-07-22 16:30:51.294 fuse! ---- progress: 63
//<--- It crashed at this moment, then I restarted the program
2022-07-22 16:31:14.311 OpenGL Vendor: "NVIDIA Corporation"
2022-07-22 16:31:14.313 Renderer Identifier: "NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2"
2022-07-22 16:31:14.314 OpenGL Version: "4.6.0 NVIDIA 512.77"
2022-07-22 16:31:14.315 GLSL Version: "4.60 NVIDIA"
2022-07-22 16:31:14.315 OpenGL version supported by this platform: "4.6.0 NVIDIA 512.77"
2022-07-22 16:31:15.873 init<discovery camera>! ---- query cameras!
2022-07-22 16:31:15.874 init<discovery camera>! ---- does NOT find device!
2022-07-22 16:31:17.033 "https://api.infly3d.com/api/ota/version/info" http post data: "{\n \"code\": \"0007\",\n \"deploy\": \"test\",\n \"versionNumber\": \"403\"\n}\n"
2022-07-22 16:31:18.043 http response data: "{\"msg\":\"未发现新版本.\",\"data\":null,\"code\":1000}"
2022-07-22 16:31:19.616 callback<device Change>! ---- added device count: 1 ,removed device count: 0
2022-07-22 16:31:21.619 start<start camera>! ---- device status: 0
2022-07-22 16:31:21.652 success<start camera>! ---- connect Camera!
2022-07-22 16:31:21.654 success<start camera>! ---- get Camera info!
2022-07-22 16:31:21.704 Read camera file(camera path): /data/camparam/LC_RT.bin
2022-07-22 16:31:21.717 Read camera file(destination path): C:/Users/arifg/handylookdata/data/LC_RT.bin
2022-07-22 16:31:21.718 Read camera file error code = 0 ---- file size: 48
2022-07-22 16:31:21.720 Read camera file(camera path): /data/camparam/Distort.bin
2022-07-22 16:31:21.737 Read camera file(destination path): C:/Users/arifg/handylookdata/data/Distort.bin
2022-07-22 16:31:21.738 Read camera file error code = 0 ---- file size: 20
2022-07-22 16:31:21.738 Read camera file(camera path): /data/camparam/Pl.bin
2022-07-22 16:31:21.756 Read camera file(destination path): C:/Users/arifg/handylookdata/data/Pl.bin
2022-07-22 16:31:21.757 Read camera file error code = 0 ---- file size: 40
2022-07-22 16:31:21.758 Read camera file(camera path): /data/camparam/camparamLR/Q.bin
2022-07-22 16:31:21.777 Read camera file(destination path): C:/Users/arifg/handylookdata/data/Q.bin
2022-07-22 16:31:21.778 Read camera file error code = 0 ---- file size: 64
2022-07-22 16:31:21.779 Read camera file(camera path): /data/camparam/mapparamL.bin
2022-07-22 16:31:21.796 Read camera file(destination path): C:/Users/arifg/handylookdata/data/mapparamL.bin
2022-07-22 16:31:21.798 Read camera file error code = 0 ---- file size: 148
2022-07-22 16:31:21.800 Read camera file(camera path): /data/camparam/mapparamR.bin
2022-07-22 16:31:21.816 Read camera file(destination path): C:/Users/arifg/handylookdata/data/mapparamR.bin
2022-07-22 16:31:21.818 Read camera file error code = 0 ---- file size: 148
2022-07-22 16:31:21.820 Read camera file(camera path): /data/camparam/Prgb.bin
2022-07-22 16:31:21.846 Read camera file(destination path): C:/Users/arifg/handylookdata/data/Prgb.bin
2022-07-22 16:31:21.847 Read camera file error code = 0 ---- file size: 40
2022-07-22 16:31:21.849 start depth stream Info: 640 400 5 3
2022-07-22 16:31:23.855 success<start depth stream>! ---- start stream!
2022-07-22 16:31:23.883 start rgb stream Info: 1280 800 30 0
2022-07-22 16:31:23.905 success<start color stream>! ---- start stream!
2022-07-22 16:31:24.984 set frame time : 7000
2022-07-22 16:31:24.987 set default exposure : 5000
2022-07-22 16:31:25.017 set rgb auto!
2022-07-22 16:31:25.084 set accuracy mode : false
2022-07-22 16:31:25.110 set accuracy mode : false
2022-07-22 16:31:25.224 set exposure : 3000
2022-07-22 16:31:36.022 --ProjectListWidget::deleteRow: 0 "{1006b12e-0d3c-4743-a7f4-f58d851f6865}" 3
Hi arifg sorry for the delay in reply.
Would you please send us your
Computer Specs
And Operating system and version of it.
I have taken note and will log the issue with our Technical Department.
Best Regards
System:
| Item | Value |
|---|---|
| OS Name | Microsoft Windows 10 Pro |
| Version | 10.0.19043 Build 19043 |
| Other OS Description | Not Available |
| OS Manufacturer | Microsoft Corporation |
| System Manufacturer | Micro-Star International Co., Ltd. |
| System Model | MS-7D25 |
| System Type | x64-based PC |
| System SKU | Default string |
| Processor | 12th Gen Intel(R) Core™ i7-12700K, 3610 Mhz, 12 Core(s), 20 Logical Processor(s) |
| BIOS Version/Date | American Megatrends International, LLC. 1.10, 12/13/2021 |
| SMBIOS Version | 3.4 |
| Embedded Controller Version | 255.255 |
| BIOS Mode | Legacy |
| BaseBoard Manufacturer | Micro-Star International Co., Ltd. |
| BaseBoard Product | PRO Z690-A WIFI DDR4(MS-7D25) |
| BaseBoard Version | 1.0 |
| Platform Role | Desktop |
| Secure Boot State | Unsupported |
| PCR7 Configuration | Binding Not Possible |
| Windows Directory | C:\WINDOWS |
| System Directory | C:\WINDOWS\system32 |
| Boot Device | \Device\HarddiskVolume1 |
| Locale | USA |
| Hardware Abstraction Layer | Version = 10.0.19041.1806 |
| Time Zone | Mountain Daylight Time |
| Installed Physical Memory (RAM) | 32.0 GB |
| Total Physical Memory | 31.8 GB |
| Available Physical Memory | 17.4 GB |
| Total Virtual Memory | 65.8 GB |
| Available Virtual Memory | 35.1 GB |
| Page File Space | 34.0 GB |
| Page File | C:\pagefile.sys |
| Kernel DMA Protection | Off |
| Virtualization-based security | Not enabled |
| Device Encryption Support | Reasons for failed automatic device encryption: PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable |
| Hyper-V - VM Monitor Mode Extensions | Yes |
| Hyper-V - Second Level Address Translation Extensions | Yes |
| Hyper-V - Virtualization Enabled in Firmware | Yes |
| Hyper-V - Data Execution Protection | Yes |
Video:
| Item | Value |
|---|---|
| Name | NVIDIA GeForce RTX 3080 Ti |
| PNP Device ID | PCI\VEN_10DE&DEV_2208&SUBSYS_389B1462&REV_A1\4&209E2803&0&0008 |
| Adapter Type | NVIDIA GeForce RTX 3080 Ti, NVIDIA compatible |
| Adapter Description | NVIDIA GeForce RTX 3080 Ti |
| Adapter RAM | (1,048,576) bytes |
| Installed Drivers | C:\WINDOWS\System32\DriverStore\FileRepository\nvmdi.inf_amd64_410df974fae868d3\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmdi.inf_amd64_410df974fae868d3\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmdi.inf_amd64_410df974fae868d3\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmdi.inf_amd64_410df974fae868d3\nvldumdx.dll |
| Driver Version | 30.0.15.1277 |
| INF File | oem167.inf (Section028 section) |
| Color Planes | Not Available |
| Color Table Entries | 4294967296 |
| Resolution | 2560 x 1080 x 60 hertz |
| Bits/Pixel | 32 |
| Memory Address | 0x63000000-0x63FFFFFF |
| Memory Address | 0x50000000-0x5FFFFFFF |
| Memory Address | 0x60000000-0x61FFFFFF |
| I/O Port | 0x00005000-0x0000507F |
| IRQ Channel | IRQ 4294967284 |
| I/O Port | 0x000003B0-0x000003BB |
| I/O Port | 0x000003C0-0x000003DF |
| Memory Address | 0xA0000-0xBFFFF |
| Driver | C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVMDI.INF_AMD64_410DF974FAE868D3\NVLDDMKM.SYS (30.0.15.1277, 40.36 MB (42,322,640 bytes), 5/19/2022 12:23 AM) |
| Name | Intel(R) UHD Graphics 770 |
| PNP Device ID | PCI\VEN_8086&DEV_4680&SUBSYS_7D251462&REV_0C\3&11583659&0&10 |
| Adapter Type | Intel(R) UHD Graphics Family, Intel Corporation compatible |
| Adapter Description | Intel(R) UHD Graphics 770 |
| Adapter RAM | 1.00 GB (1,073,741,824 bytes) |
| Installed Drivers | <>,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_66738090704aeb53\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_66738090704aeb53\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_66738090704aeb53\igd12umd64.dll |
| Driver Version | 31.0.101.3222 |
| INF File | oem183.inf (iADLSD_w10_DS section) |
| Color Planes | Not Available |
| Color Table Entries | Not Available |
| Resolution | Not Available |
| Bits/Pixel | Not Available |
| Memory Address | 0x62000000-0x62FFFFFF |
| Memory Address | 0x40000000-0x4FFFFFFF |
| I/O Port | 0x00006000-0x0000603F |
| IRQ Channel | IRQ 4294967283 |
| Driver | C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_66738090704AEB53\IGDKMDN64.SYS (31.0.101.3222, 42.67 MB (44,741,176 bytes), 7/28/2022 9:17 AM) |
Disk Drives:
| Description | Disk drive |
|---|---|
| Manufacturer | (Standard disk drives) |
| Model | WDC WD40EZRZ-00GXCB0 |
| Bytes/Sector | 512 |
| Media Loaded | Yes |
| Media Type | Fixed hard disk |
| Partitions | 1 |
| SCSI Bus | 1 |
| SCSI Logical Unit | 0 |
| SCSI Port | 0 |
| SCSI Target ID | 0 |
| Sectors/Track | 63 |
| Size | 3.64 TB (4,000,784,417,280 bytes) |
| Total Cylinders | 486,401 |
| Total Sectors | 7,814,032,065 |
| Total Tracks | 124,032,255 |
| Tracks/Cylinder | 255 |
| Partition | Disk #1, Partition #0 |
| Partition Size | 3.64 TB (4,000,768,327,680 bytes) |
| Partition Starting Offset | 16,777,216 bytes |
| Description | Disk drive |
| Manufacturer | (Standard disk drives) |
| Model | Samsung SSD 860 EVO 2TB |
| Bytes/Sector | 512 |
| Media Loaded | Yes |
| Media Type | Fixed hard disk |
| Partitions | 3 |
| SCSI Bus | 0 |
| SCSI Logical Unit | 0 |
| SCSI Port | 0 |
| SCSI Target ID | 0 |
| Sectors/Track | 63 |
| Size | 1.82 TB (2,000,396,321,280 bytes) |
| Total Cylinders | 243,201 |
| Total Sectors | 3,907,024,065 |
| Total Tracks | 62,016,255 |
| Tracks/Cylinder | 255 |
| Partition | Disk #0, Partition #0 |
| Partition Size | 48.00 MB (50,331,648 bytes) |
| Partition Starting Offset | 1,048,576 bytes |
| Partition | Disk #0, Partition #1 |
| Partition Size | 1.82 TB (1,999,746,629,632 bytes) |
| Partition Starting Offset | 51,380,224 bytes |
| Partition | Disk #0, Partition #2 |
| Partition Size | 573.00 MB (600,834,048 bytes) |
| Partition Starting Offset | 1,999,798,009,856 bytes |
| Description | Disk drive |
| Manufacturer | (Standard disk drives) |
| Model | Seagate Backup+ Hub BK SCSI Disk Device |
| Bytes/Sector | 512 |
| Media Loaded | Yes |
| Media Type | External hard disk media |
| Partitions | 1 |
| SCSI Bus | 0 |
| SCSI Logical Unit | 0 |
| SCSI Port | 1 |
| SCSI Target ID | 0 |
| Sectors/Track | 63 |
| Size | 4.55 TB (5,000,978,465,280 bytes) |
| Total Cylinders | 608,001 |
| Total Sectors | 9,767,536,065 |
| Total Tracks | 155,040,255 |
| Tracks/Cylinder | 255 |
| Partition | Disk #2, Partition #0 |
| Partition Size | 4.55 TB (5,000,845,590,528 bytes) |
| Partition Starting Offset | 135,266,304 bytes |
I am guessing you run out of RAM while fussing some of your scans since fusing process use mostly RAM to process it , some of my fusing process need sometimes even 32GB to process it .
How more overlapped the scans while scanning , how more RAM it will use to clean the overlap framed before fuse it . It would be helpful to monitor the process via Task Manager and see how much RAM was used while fussing at the moment of crash of the software to be 100% sure .
From your info I see that you have only available around 17GB what may be the case as you stated it don’t happens all the time .
I am using the software since last year and never experienced any crash and I really pushing it to the limits while testing it out with huge scans .
17GB should be enough for use with POP2 but the last software increased the quality and the point cloud is rather dense compared to early versions what can cause the out of memory issue and crash your software .
I currently have 32GB of RAM available, isn’t it enough? Returning your own words previously spoken: how people use their phones or less powerful PC’s to do the scans?
From your own info , there was only 17 GB of RAM available , the system and graphic card also use your RAM so you have not 32GB available for use with Revo Scan .
Phone and tablets fusing the point cloud at higher values for the pitch point resolution than computers , so it don’t need that much RAM to process and if there is not enough RAM available it would limit how much frames you can capture to prevent crashing .
On computers the limitation do not prevent you from capturing more frames than your computer can handle .
I am scanning sometimes objects that are 2 inches only and Revo Scan use more RAM than your system has available to deal with .
I just give you an idea to check out the process on your system so you know what is going on , not all systems are the same , on one it works flawless on other it don’t .
From your own info , there was only 17 GB of RAM available
Well, it is obvious that OS and processes use memory. So, on a computers with 16GB of physical RAM only 6-7GB available, on computers with 8Gb of RAM - just 4GB is free and so on. So even though I have just 17GB available, those with less RAM have even less and my remark still stay in effect. Besides that, there is such thing as Virtual Memory, which is used when not enough physical RAM is available, so if some active process requests memory, OS manages other less active processes to swap their currently idle pages of memory to disk to allocate as much of physical memory as possible to the process-requestor. There are also multiple measures in the kernel to commit large blocks of contiguous memory chunks, as well as look-aside lists of memory blocks to prevent memory segmentation, which can be used to optimize the memory allocation for memory-hungry processes on the systems with deficit of physical resources. Are you trying to convince me that the more physical RAM in the system - the less is available for Revo Scan?! 17GB of available memory is still more than physical RAM installed on the 50% of all consumer-rated computers on the market.
I don’t try to convince you , but give you some tip .
I hope you find your way out
Good luck !
How can I find my way out myself if the program crashes arbitrarily? Unless I have the source code and debug it myself here.
Try another computer, different file, change whatever you can…
1 Like
Good advice. Super! 
I will give it to all customers of our company when they will complain about software we’re developing.
1 Like