-
Notifications
You must be signed in to change notification settings - Fork 230
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
getPixelDataFromFragments - Bad Uint8Array initialization #38
Comments
Can you provide a sample dataset and fix via PR? Thanks |
Attached a sample dataset. I will submit the PR next week. |
I think I may have fixed this in 1.4.3, can you please test? |
I apologize for not posting the additional info you requested but my Sorry for not being more helpful On Fri, May 20, 2016 at 3:02 PM, Chris Hafey notifications@github.com
|
Closing |
I found a strange behavior in the case of a single fragment and a new Uint8Array is crated as a view of the dicom object byteStream: the new array is misaligned from the source buffer.
In my case the new array is two bytes ahead: fragments[0].dataOffset is 2056, the new array starts at byte 2054 of the byteStream. Length is correct.
I found this behavior using Safari on Mac OS X, Chrome and Firefox on Ubuntu Linux x64, Chrome on Windows 7 x64. Could be a dword alignment? but 2056 is at dword boundaries!
The work around I applied is to comment the if( fragments.lenght === 1) condition.
The text was updated successfully, but these errors were encountered: