Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataDDS: std::bad_alloc #263

Open
ndp-opendap opened this issue Nov 7, 2024 · 0 comments
Open

DataDDS: std::bad_alloc #263

ndp-opendap opened this issue Nov 7, 2024 · 0 comments

Comments

@ndp-opendap
Copy link
Contributor

ndp-opendap commented Nov 7, 2024

When I tried to get a DAP2 Data Response:

http://test.opendap.org:8080/opendap/ghrsst/20210102090000-JPL-L4_GHRSST-SSTfnd-MUR-GLOB-v02.0-fv04.1.h5.dods?/analysed_sst[0][0:17998][0:29827]

(Unencoded URL for readability)

I see the following error:

Dataset {
    Int16 /analysed_sst[1][17999][29828];
} 20210102090000-JPL-L4_GHRSST-SSTfnd-MUR-GLOB-v02.0-fv04.1.h5;
Data:
Error { 
    code = 500;
    message = "std::exception caught transmitting DataDDS: std::bad_alloc (caught in BESDapTransmit).";
}

The variable size is about 1/2 of the 2GB limit, but it may be the case that since the data are Int16 that they are getting "padded" in XDR and more than a In32 can hop:

Int16

  • 2^30 - (17999 * 29827 * 2) = 29478
    -b 2^30 - (17999 * 29828 * 2) = -6520

Int16 padded to Int32 by XDR?

  • 2^31 - (17999 * 29827 * 4) = 58956
  • 2^31 - (17999 * 29828 * 4) = -13040
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant