c++ - mmap call takes too long (>100 seconds) -


We are currently looking at taking our processes with the mmap call for a very long time. Once the process reaches approximately ~ 2.8 GB, the MMAP takes the call to 100 seconds and is killed by the heart beat mechanism created in this process. Anyone would like to know this problem or will know why it will take more than 100 seconds when asked for memory.

Host and compiler information:

  • Host memory: 70 GB OS: All files, Redhat 6.3 compiler: GCC 4.4.6 process memory limit (32 bit): 4 GB no swap configured

And if this happens, the host still has 50GB of storage remaining.

Stack trace:

  # 0,55575430 in __kernel_vsyscall () from # 1 0x560f9dd8 mmap () to /lib/libc.so.6 # 2 0x5608f2db New (unsigned int) () /usr/lib/libstdc++.so.6 in /lib/libc.so.6 # 4 0x55fb509a operator from / lib / libc in .so.6 # 3 0x5608fb7e mloc () # 5 0x55f91ed6 std :: out of the original_string & lt; Char, std :: char_traits & lt; Char & gt ;, std :: allocator & lt; Char & gt; & Gt; :: _ Rep: _ S_create (unsigned int, unsigned int, std :: allocator & lt; char> const & amp;) () /usr/lib/libstdc++.so.6 to  


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

c# - MySQL Parameterized Select Query joining tables issue -