-
Notifications
You must be signed in to change notification settings - Fork 16
Memory Leak when running sick_scan_caller #19
Comments
Dr. Memory version 2.5.0 build 0 built on Oct 18 2021 03:10:43 Error /#1: UNINITIALIZED READ: reading register cl Error /#2: UNINITIALIZED READ: reading register al Error /#3: UNINITIALIZED READ: reading 0x074c67f0-0x074c67f1 1 byte(s) Error /#4: UNINITIALIZED READ: reading 0x074c67b0-0x074c67b1 1 byte(s) Error /#5: UNINITIALIZED READ: reading 0x074c6828-0x074c682c 4 byte(s) Error /#6: LEAK 28 direct bytes 0x06cc00f8-0x06cc0114 + 0 indirect bytes Error /#7: LEAK 28 direct bytes 0x06cc0138-0x06cc0154 + 0 indirect bytes Error /#8: LEAK 28 direct bytes 0x06cc0178-0x06cc0194 + 0 indirect bytes =========================================================================== DUPLICATE ERROR COUNTS: SUPPRESSIONS USED: ERRORS FOUND: |
I noticed that the memory leak was originated from pthreadw32, so does it seem to be necessary to deploy sick_scan_xd to prevent this problem? |
Thanks for reporting and analyzing this issue! The memory leak is caused by a missing |
I tried running sick_scan_caller, and everything went fine.
But I noticed that the memory it cost went up and didn't seem to stop rising.
So I tried using Dr.Memory to detect memory leak, and the report shows that it does.
Report is shown in next chat box.
Btw, my device is sick tim 561, and the program was running on Windows10.
So how could we fix this?
The text was updated successfully, but these errors were encountered: