ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Thanks ahendrix for leading me in the right direction. After you pointed the problem with memory allocation, I read a little bit more about how memory allocation works with processes. I am running a 32-bit OS which limits to 2.75 - 3 GB address allocation memory, which is close to 18.4% of 16GB (= 2.94GB). So I'm definitely hitting memory limit. (Reference: http://en.wikipedia.org/wiki/3_GB_barrier)

Having the rosbag run at different speeds, and still failing at 18.4% memory usage every time makes sure that the above error is because I'm using a 32-bit machine.

I'll try running it on a 64-bit computer, and post the limitations (if any) of using octomap with 64 bit.

Thanks ahendrix for leading me in the right direction. After you pointed out the problem with memory allocation, I read a little bit more about how memory allocation works with processes. I am running a 32-bit OS which limits to 2.75 - 3 GB address allocation memory, which is close to 18.4% of 16GB (= 2.94GB). So I'm definitely hitting memory limit. (Reference: http://en.wikipedia.org/wiki/3_GB_barrier)

Having the rosbag run at different speeds, and still failing at 18.4% memory usage every time makes sure that the above error is because I'm using a 32-bit machine.

I'll try running it on a 64-bit computer, and post the limitations (if any) of using octomap with 64 bit.

Thanks ahendrix for leading me in the right direction. After you pointed out the problem with memory allocation, I read a little bit more about how memory allocation works with processes. I am running a 32-bit OS which limits to 2.75 - 3 GB address allocation memory, which is close to 18.4% of 16GB (= 2.94GB). So I'm definitely hitting memory limit. (Reference: http://en.wikipedia.org/wiki/3_GB_barrier)

Having the rosbag run at different speeds, and still failing at 18.4% memory usage every time makes sure that the above error is because I'm using a 32-bit machine.

I'll try running it on a 64-bit computer, and post the limitations (if any) of using octomap with 64 bit.

Edit: Now that I'm on a 64-bit machine (with 32GB RAM), I tried mappusing octomap. The system monitoring stats show that octomap at its peak uses up toing an outdoor area of around 100mx20m (post processing on recorded data) 50% of memory (range- 35-50%) along multiple processes running on multiple processors (using at least 1 complete core). Now I am convinced that a 64-bit machine with 16+GB RAM is a minimum requirement for building octomap for large areas.