You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I ran my own app, it reports below error:
CTOR: couldn't allocate memory for caching chunks, invalid/check size?
libc++abi: terminating with uncaught exception of type h5::error::io::packet_table::misc:
H5Dappend.hpp line# 167 : CTOR: unable to create handle from dataset...
Below are minimum code to demo the error, when the block_size (1110) is not multiple of H5CPP_MEM_ALIGNMENT (64).
It will report the error. Any idea to bypass this error or fix it?
Replacing "aligned_alloc" with normal "alloc" could be an option when the block_size % H5CPP_MEM_ALIGNMENT != 0
Hi @steven-varga and H5CPP:
By using h5cpp recently, I found a potential bug (not 100% sure) in the code for the function pipeline_t::set_cache
h5cpp/h5cpp/H5Zpipeline.hpp
Line 137 in 1444cf8
When I ran my own app, it reports below error:
CTOR: couldn't allocate memory for caching chunks, invalid/check size?
libc++abi: terminating with uncaught exception of type h5::error::io::packet_table::misc:
H5Dappend.hpp line# 167 : CTOR: unable to create handle from dataset...
Below are minimum code to demo the error, when the block_size (1110) is not multiple of H5CPP_MEM_ALIGNMENT (64).
It will report the error. Any idea to bypass this error or fix it?
Replacing "aligned_alloc" with normal "alloc" could be an option when the block_size % H5CPP_MEM_ALIGNMENT != 0
Bests,
Bin
#define H5CPP_MEM_ALIGNMENT 64
#include <stdio.h>
#include <stdlib.h>
#include
#include
#include
#include
#include
#include
#include
int main()
{
size_t block_size = 1110;
char *chunk0, *chunk1;
}
The aligned_alloc seems to require "the size parameter must be an integral multiple of alignment."
https://en.cppreference.com/w/c/memory/aligned_alloc
void *aligned_alloc( size_t alignment, size_t size );
The text was updated successfully, but these errors were encountered: