Input.cc uses H5Dget_storage_size to determine how much memory to allocate for the large string attributes (Paramters and grid structure). However this function literally returns the space used on disk which differs from the space in memory when compression is used (or when the dataset is sparse, or when the datatype on disk is different from that in memory eg float vs double).
The attached patch instead queries the dataspace for the number of points.
Ok to apply? Is there a preferred way of getting this size othewise?