Uh oh!
There was an error while loading. Please reload this page.
test: disable test-crypto-secure-heap with asan - #36900
Conversation
nodejs-github-bot
commented
Jan 12, 2021
aduh95
commented
Jan 12, 2021
fast-track? |
nodejs-github-bot
commented
Jan 12, 2021
jasnell
commented
Jan 12, 2021
Just waiting on the last CI run to finish then will land this... |
jasnell
commented
Jan 12, 2021
Landed in eef75a957c38 |
aduh95
commented
Jan 12, 2021
There is no commit eef75a957c38 on master.. |
The asan checks don't play well currently with persistent secure heap allocations. Signed-off-by: James M Snell <jasnell@gmail.com> PR-URL: nodejs#36900 Refs: nodejs#36881 Reviewed-By: Danielle Adams <adamzdanielle@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com>
3460b40 to
6e3a832Compareaduh95
commented
Jan 12, 2021
Landed in 6e3a832 |
The asan checks don't play well currently with persistent secure heap allocations. Signed-off-by: James M Snell <jasnell@gmail.com> PR-URL: #36900 Refs: #36881 Reviewed-By: Danielle Adams <adamzdanielle@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com>
addaleax
commented
Jan 16, 2021
Okay, but shouldn't there be at least a TODO comment for actually fixing this memory leak? It doesn't look like there's a call to |
jasnell
commented
Jan 17, 2021
Forgot the todo but adding the |
The asan checks don't play well currently with persistent secure
heap allocations.
Signed-off-by: James M Snell jasnell@gmail.com
Refs: #36881