launch problem terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc

[kxc12689]

After I correctly installed LIVOXSDK2 and build livox_ros_driver2. Then I run roslaunch livox_ros_driver2 msg_MID360.launch

Then the ros process initiating shutdown.Here are the output: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc REQUIRED process [livox_lidar_publisher2-2] has died! process has died [pid 7268, exit code -6, cmd /home/k/Project/ws_livox/devel/lib/livox_ros_driver2/livox_ros_driver2_node 47MDL610010087 __name:=livox_lidar_publisher2 __log:=/home/k/.ros/log/50db33b6-35c4-11ee-91d5-08bfb82db560/livox_lidar_publisher2-2.log]. log file: /home/k/.ros/log/50db33b6-35c4-11ee-91d5-08bfb82db560/livox_lidar_publisher2-2*.log Initiating shutdown!

The problem looks connected to LivoxViewer2 too. I have tested on 4 different machines, only 2 can run correctly, the others all have the problem above. At the same time, the livox_ros_driver2 run abnormally also have problem when run ./Livoxviewer2.sh. Outputs need run using opengl4.3 and ./Livoxviewer2.sh -opengl3 still useless.

Please give some support.

[Marabir]

I have the same problem but during launching rviz_MID.launch but I don't know how to fix it. Does the error occur also with this launch?

[kxc12689]

I have the same problem but during launching rviz_MID.launch but I don't know how to fix it. Does the error occur also with this launch?

All the launch files in livox_ros_driver2 about ROS1 have the problem. I think there must have some bug undetected in LIVOXSDK2.

[Snowbound9173]

Same error. This is my first time installing the driver after they pulled down the repository a few weeks ago and then only recently re-uploaded it.

Were there changes? It worked before they pulled the driver down..

Edit: I'm trying to run msg_HAP

[kxc12689]

Today got a new phenomenon. Two mechine I tested result in error became normal today, so strange.

[trishmapow]

Same issue after "upgrading" to the re-released SDK2. One device works, other doesn't.

[trishmapow]

Turned out to not be a problem with SDK. Reverted driver to v1.1.3 and now working again. git checkout 4f40ab789d7305207a3b371f635b114068b68601

[Call-Me-Jesse]

I have not encountered this problem, are you using version 1.2.2 ? by the way, The ros driver needs to be placed in the src directory.

[kxc12689]

I have not encountered this problem, are you using version 1.2.2 ? by the way, The ros driver needs to be placed in the src directory.

Yes, its v1.2.2. The package correctly places in workspace/src/.

[Call-Me-Jesse]

I have not encountered this problem, are you using version 1.2.2 ? by the way, The ros driver needs to be placed in the src directory.

Yes, its v1.2.2. The package correctly places in workspace/src/.

I am using 1.2.1 and have not encountered this problem, you can try this version, maybe it will solve the problem

[YCJin9]

I use LivoxViewer2 set host ip can solve this problem

[Marabir]

I use LivoxViewer2 set host ip can solve this problem

so I have to set host ip with LivoxViewer2? I will check it on Monday.

[Call-Me-Jesse]

I use LivoxViewer2 set host ip can solve this problem

so I have to set host ip with LivoxViewer2? I will check it on Monday.

I found that 1.2.3 version does not have this problem, instead of set host ip with LivoxViewer2, try 1.2.3 version.

[YCJin9]

I use LivoxViewer2 set host ip can solve this problem

so I have to set host ip with LivoxViewer2? I will check it on Monday.

I found that 1.2.3 version does not have this problem, instead of set host ip with LivoxViewer2, try 1.2.3 version.

ok, i‘ll try it