8000 Segmentation fault when calling build_ivf in Retriever.__call__ with input shape (900, 1024) · Issue #128 · naver/mast3r · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Segmentation fault when calling build_ivf in Retriever.__call__ with input shape (900, 1024) #128
Open
@ZYX-MLer

Description

@ZYX-MLer

I’m encountering a segmentation fault when running the following line in Retriever.call: running on my macbook

asmk_dataset = self.asmk.build_ivf(feat, ids)

•	feat has shape (900, 1024) and dtype float32
•	ids has shape (900,) and dtype int64

The system crashes with the following output:

*** Aborted at 1748440365 (unix time) try "date -d @1748440365" if you are using GNU date ***
PC: @ 0x0 (unknown)
*** SIGSEGV (@0x540) received by PID 2851 (TID 0x312827000) stack trace: ***
@ 0x19a2803e8 (unknown)
@ 0x1031875d4 (unknown)
@ 0x19a39c624 (unknown)
@ 0x102830990 (unknown)
@ 0x102830990 (unknown)
@ 0x141b96c1c (unknown)
@ 0x141b92e4c (unknown)
@ 0x141b95aa4 (unknown)
@ 0x141b7a620 (unknown)
@ 0x141bafae8 (unknown)
@ 0x19a362c0c (unknown)
@ 0x19a35db80 (unknown)
/Users/zyx/miniconda3/envs/3R/lib/python3.10/multiprocessing/resource_tracker.py:224: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d '

I’m using FAISS and ASMK under Python 3.10 on macOS with a virtual environment. The crash occurs consistently at this point.

Please let me know if there is a known issue with build_ivf under these conditions or if you need further information such as environment details, FAISS version, or a minimal reproducible example.

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0