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
Which may address this at some point, since the current hash block object types are:
pubenumHashBlockObjectType{Cai,Xmp,Other,}
With that said, the current code simply clumps all HashBlockObjectType::Cai types together to have one range. This could be an issue where an asset type has the "Cai" block split in two different areas of the file (e.g., the beginning in a lookup table and the end).
In our work we have added the ability to treat each HashBlockObjectType::Cai as an exclusion range, de-fragmenting any areas that are adjacent to each other in memory.
Note: I plan to subsequently raise a PR for this
The text was updated successfully, but these errors were encountered:
From our understanding, the data hashes, should allow for multiple exclusions. Searching through the "Issues", I found:
#560
Which may address this at some point, since the current hash block object types are:
With that said, the current code simply clumps all
HashBlockObjectType::Cai
types together to have one range. This could be an issue where an asset type has the "Cai" block split in two different areas of the file (e.g., the beginning in a lookup table and the end).In our work we have added the ability to treat each
HashBlockObjectType::Cai
as an exclusion range, de-fragmenting any areas that are adjacent to each other in memory.The text was updated successfully, but these errors were encountered: