Skip to content

[BUG]: gnn_fraud_detection_pipeline example intermittently segfaults on shutdown #810

Closed
@dagardner-nv

Description

Version

23.03

Which installation method(s) does this occur on?

Source

Describe the bug.

Seen in PR #758 happens roughly 1/10 runs I get a segfault on shutdown, and unfortunately I can't get it to generate a core dump.

Graph construction rate[Complete]: 265 messages [00:00, 2959.73 messages/s]
Inference rate[Complete]: 265 messages [00:03, 73.04 messages/s]
Add classification rate[Complete]: 265 messages [00:03, 72.50 messages/s]
Serialize rate[Complete]: 265 messages [00:03, 71.42 messages/s]
====Pipeline Complete====
*** Aborted at 1680026004 (unix time) try "date -d @1680026004" if you are using GNU date ***
PC: @                0x0 (unknown)
*** SIGSEGV (@0x0) received by PID 2987396 (TID 0x7f330cc6b740) from PID 0; stack trace: ***
    @     0x7f330bfd0197 google::(anonymous namespace)::FailureSignalHandler()
    @     0x7f330ca3daa0 (unknown)
    @     0x7f2fa920571c std::_Hashtable<>::find()
    @     0x7f2fa920e901 _ZNSt19_Sp_counted_deleterIPN4raft13interruptibleEZNS1_14get_token_implILb1EEESt10shared_ptrIS1_ENSt6thread2idEEUlT_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv  
    @     0x7f2fa91de380 std::shared_ptr<>::~shared_ptr()
    @     0x7f330b4faf2c (anonymous namespace)::run()
    @     0x7f330ca3ffb5 (unknown)
    @     0x7f330ca4012a exit
    @     0x55e28a690631 Py_Exit
    @     0x55e28a690580 handle_system_exit
    @     0x55e28a690253 _PyErr_PrintEx
    @     0x55e28a698b22 PyRun_SimpleFileExFlags
    @     0x55e28a68c173 Py_RunMain.cold
    @     0x55e28a7ccc49 Py_BytesMain
    @     0x7f330ca2920a (unknown)
    @     0x7f330ca292bc __libc_start_main
    @     0x55e28a7ccb55 (unknown)
Segmentation fault

Minimum reproducible example

mamba env update -n ${CONDA_DEFAULT_ENV} -f examples/gnn_fraud_detection_pipeline/requirements.yml
cd examples/gnn_fraud_detection_pipeline
python run.py

This is also reproducible using the morpheus CLI tool

Relevant log output

No response

Full env printout

No response

Other/Misc.

No response

Code of Conduct

  • I agree to follow Morpheus' Code of Conduct
  • I have searched the open bugs and have found no duplicates for this bug report

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    • Status

      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions