ceezous

Dr. Memory version 2.5.0 build 0 built on Oct 18 2021 03:10:43 Windows version: WinVer=105;Rel=2009;Build=19043;Edition=Enterprise Dr. Memory results for pid 22352: "sick_generic_caller.exe" Application cmdline: "./sick_generic_caller.exe ../../launch/sick_tim_5xx.launch hostname:=192.168.1.100" Recorded 124 suppression(s)...

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?

@rostest Thanks for the reply. I would like to switch to the sick_scan_xd driver if I have more time, but my team has already implement the previous lib (sick_scan_base) in...

Sure. I added some log into sick_scan_base and output it in a file. I manually disconnected the laser physically and reconnected, I found that it will try to reconnect about...

Sorry for this late reply. We're using SickTim561. And I'll paste the log in next chat box. For convenience, here is some useful info: the restarting process lasts from 17:35:34.823...

new sick laser ROS_INFO: Publishing laserscan-pointcloud2 to [Info],2022-03-31 17:35:33.456,5492,Func 'SickTim561Official' start. [Info],2022-03-31 17:35:33.456,5492,Func 'SickTim561Official' end. [Info],2022-03-31 17:35:33.456,5492,Func 'open' start. [Info],2022-03-31 17:35:33.456,5492,Func 'set_looping_state' start. [Info],2022-03-31 17:35:33.456,5492,Func 'set_looping_state': New state is '0'...

> Visual Studio 2019 is recommended for the Windows build. If you're using Visual Studio 2017 (which "libboost_system-vc141" suggests), try upgrading to Visual Studio 2019. Thank you for your replay....

> It works. I applied both libs(personal lib and sick_scan_base) with boost 1.68, and the exact problem seems to be solved.