ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
The freezes I encounter are usually either due to disk i/o (especially memory swapping) or hardware drivers. I guess the latter can be excluded, so you should monitor the memory exhaustion (e.g. use watch -n 0.5 free -m
). If this is the problem, you might try to disable swap (sudo swapoff -a
), so the compilation is killed when the physical memory is full.
2 | No.2 Revision |
The freezes I encounter are usually either due to disk i/o (especially memory swapping) or hardware drivers. I guess the latter can be excluded, so you should monitor the memory exhaustion (e.g. use watch -n 0.5 free -m
). If this is the problem, you might You may try to disable swap (sudo swapoff -a
), so the compilation is just killed when the physical memory is full.
I am not sure whether catkin_make_isolated automatically parallelizes. If so, you might want to disable that (maybe append "-j1"?).
3 | No.3 Revision |
The freezes I encounter are usually either due to disk i/o (especially memory swapping) or hardware drivers. I guess the latter can be excluded, so you should monitor the memory exhaustion (e.g. use watch -n 0.5 free -m
). You may try to disable swap (sudo swapoff -a
), so the compilation is just killed when the physical memory is full.
Edit:
I am not sure whether catkin_make_isolated automatically parallelizes. If so, you might want to disable that (maybe append "-j1"?).
If it is the memory problem and disabling parallelization doesn't help, try to lower the complexity of the compilation of the problematic files.
Otherwise, getting more RAM is usually an option.
The above are just ideas from the top of my head. Make sure it is the memory swapping problem first.
4 | No.4 Revision |
The freezes I encounter are usually either due to disk i/o (especially memory swapping) or hardware drivers. I guess the latter can be excluded, so you should monitor the memory exhaustion (e.g. use watch -n 0.5 free -m
). You may try to disable swap (sudo swapoff -a
), so the compilation is just killed when the physical memory is full.
Edit:
I am not sure whether catkin_make_isolated automatically parallelizes. If so, you might want to disable that (maybe append "-j1"?).
If it is the memory problem and disabling parallelization doesn't help, try to lower the complexity of the compilation of the problematic files.
Otherwise, getting more RAM is usually an option.
The above are just ideas from the top of my head. Make sure it is the memory swapping problem first.