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
Compiling hictkpy in Release mode with Microsoft Visual Studio 17.10 (MSVC 19.40.33816.0) and newer (tested until Microsoft Visual Studio Preview 17.12.0 (Preview 2.1); 19.42.34321.1), leads to broken wheels that segfault due to heap corruptions.
I believe this to be a compiler bug, but have been unable to trigger the bug with small reproducers (even changing -DCMAKE_BUILD_TYPE from Release to RelWithDebInfo is enough to make the heap corruption go away. Also not linking with nanobindmakes the problem go away).
PR #78 introduced a check to prevent users from building hictkpy with compiler versions affected by this issue.
This is a reminder to periodically check back to see if new compiler releases address the heap corruption (and to update the above check).
Compiling hictkpy in Release mode with Microsoft Visual Studio 17.10 (MSVC 19.40.33816.0) and newer (tested until Microsoft Visual Studio Preview 17.12.0 (Preview 2.1); 19.42.34321.1), leads to broken wheels that segfault due to heap corruptions.
I believe this to be a compiler bug, but have been unable to trigger the bug with small reproducers (even changing
-DCMAKE_BUILD_TYPE
fromRelease
toRelWithDebInfo
is enough to make the heap corruption go away. Also not linking withnanobind
makes the problem go away).PR #78 introduced a check to prevent users from building
hictkpy
with compiler versions affected by this issue.This is a reminder to periodically check back to see if new compiler releases address the heap corruption (and to update the above check).
Visual Studio Release History
The text was updated successfully, but these errors were encountered: