-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
请问跑一会儿就卡死退出了,而且只对着一个方向是咋回事 #105
Comments
同问 |
when i run “roslaunch loam_livox livox.launch”,the pointcloud is often broken up, and just in a centrum. |
ask this question in detail |
同问 |
same question |
Uninstall and reinstall Ubuntu 18 or 20. Don't install opencv and use opencv 3 or 4 built by system. |
Do you solve it successfully by this method? |
Yes. I used to install opencv myself, and there came a problem after that. |
I check my opencv version, it is 3.2.0. I am hard to ensure this problem that's caused by it. |
I don't know if you have installed opencv separately after installing Ubuntu. If it is, then it's probably the problem I said, if you haven't installed opencv yourself, it should be another problem.我不知道你在安装Ubuntu之后有没有再单独安装过opencv。如果是,那很有可能是我说的问题,如果你没有自己安装过opencv,那就应该是其他问题。 |
I have the same question in ubuntu 18.04 in vmware. |
I haven’t installed opencv separately, but I use ubuntu16.04. Every time I use the rviz command to run other people’s .bag files or record my own bag files, I get stuck, with a black screen. My laptop is configured with i7- 12700h 3060 graphics card. I don't know if it's a hardware problem or what? Has anyone solved it yet? |
没有别的报错的话,应该是硬件的问题,用free -m命令试试看看内存 |
'QVector' is registered ... should be omited. The 'Warnning' just says there is a mistake. These can't be used to judge where's wrong. |
我实在虚拟机上进行操作的,给虚拟机16个处理器,运行内存也是16G,应该不是内存的问题。目前使用自己录制bag的方法(roslaunch livox_ros_driver livox_lidar_rviz.launch之后rosbag record -a)很卡。录制效果也不是很理想;使用实时建图的话基本上进入两三秒钟就会卡死,rviz视野上也只是一帧点云。不知道该怎么解决了。目前准备换一个ubuntu18.04继续试试,如果有人知道怎么解决,请告知。万分感谢。 |
请问跑一会儿就卡死退出了,而且只对着一个方向是咋回事
The text was updated successfully, but these errors were encountered: