-
Notifications
You must be signed in to change notification settings - Fork 532
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
[BUG] Memory access error in IVFPQ unit test #3318
Comments
Answers #3318 This may fix the error observed in CI. Before the change, the memory manager handler was released first, then the FAISS index. After the change, the FAISS index is released first, then the memory manager handler is released. Authors: - Victor Lafargue (@viclafargue) Approvers: - John Zedlewski (@JohnZed) URL: #3391
Answered by #3391 |
Unfortunately, even with this fix I still saw the memory access error in CI for #3304. I'm going to reopen this for now to facilitate further discussion. |
|
Also observed on CUDA 11 on #3409 |
Here is statement causing the invalid read. By looking into FAISS issues, I came across this issue mentioning this exact same statement. The problem has already been identified (even though not experienced) and a fix for it is available from FAISS 1.6.4. Basically, the bounds weren't checked. |
Following observations in #3318 Authors: - Victor Lafargue (@viclafargue) Approvers: - John Zedlewski (@JohnZed) URL: #3472
A warning was added in #3472. FAISS should be updated to a version that contains a fix for this. |
For clarity, #3459 tracks the underlying problem |
With the update to FAISS 1.7, the [previously observed issue with IVFPQ](#3318) has disappeared. However some other issues were recently identified in ANN methods. This PR updates the relevant warnings and pytests accordingly. Authors: - Victor Lafargue (https://github.com/viclafargue) Approvers: - Dante Gama Dessavre (https://github.com/dantegd) URL: #4101
With the update to FAISS 1.7, the [previously observed issue with IVFPQ](rapidsai#3318) has disappeared. However some other issues were recently identified in ANN methods. This PR updates the relevant warnings and pytests accordingly. Authors: - Victor Lafargue (https://github.com/viclafargue) Approvers: - Dante Gama Dessavre (https://github.com/dantegd) URL: rapidsai#4101
Describe the bug
As shown in the CI log for this apparently unrelated PR, one of the IVFPQ unit tests fails with a memory access error in FAISS code. I have not yet been able to reproduce this independently, but I'm opening this issue to document recurrences or anything else we find related to this problem.
The text was updated successfully, but these errors were encountered: