[GH-ISSUE #1677] CentOS7 tests may give std::bad_alloc #874

New issue

Closed

opened 2026-03-04 01:49:35 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:49:35 +03:00

Owner

Originally created by @ggtakec on GitHub (Jun 13, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1677

#1672 , #1673

Detail

In the test_concurrent_directory_updates test of CentOS7, it seems that the following error is occasionally displayed.

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

There is a possibility that memory fragmentation has occurred, or that a large memory area is reserved.
However, it is possible that the process that caused this is not just s3fs, but other programs running at the same time.

Originally created by @ggtakec on GitHub (Jun 13, 2021). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1677 ### Related Issue (PR) #1672 , #1673 ### Detail In the `test_concurrent_directory_updates` test of CentOS7, it seems that the following error is occasionally displayed. ``` terminate called after throwing an instance of 'std::bad_alloc' what():std::bad_alloc ``` There is a possibility that memory fragmentation has occurred, or that a large memory area is reserved. However, it is possible that the process that caused this is not just s3fs, but other programs running at the same time.

kerem closed this issue

2026-03-04 01:49:35 +03:00

kerem commented

2026-03-04 01:49:36 +03:00

Author

Owner

@gaul commented on GitHub (Jun 13, 2021):

I think this may be due to memory corruption if s3fs clobbers some of the malloc metadata.

@gaul commented on GitHub (Jun 13, 2021): I think this may be due to memory corruption if s3fs clobbers some of the malloc metadata.

kerem commented

2026-03-04 01:49:36 +03:00

Author

Owner

@ggtakec commented on GitHub (Jun 13, 2021):

It may be the cause you pointed out.
I think that it will take some time to investigate the cause.
(In the build after merging just before, the CentOS 7 test passed without any problems.)

@ggtakec commented on GitHub (Jun 13, 2021): It may be the cause you pointed out. I think that it will take some time to investigate the cause. (In the build after merging just before, the CentOS 7 test passed without any problems.)

kerem commented

2026-03-04 01:49:36 +03:00

Author

Owner

@ggtakec commented on GitHub (Jun 13, 2021):

@gaul Thanks.

@ggtakec commented on GitHub (Jun 13, 2021): @gaul Thanks.

kerem referenced this issue

2026-03-04 02:01:37 +03:00

[PR #874] [MERGED] Address cppcheck 1.86 errors #1673