Skip to content
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.

Sign up for GitHub

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

Jump to bottom

YOLOv9 exited with code 139 #906

Closed
trantuankhoi opened this issue Jan 8, 2025 · 2 comments
Closed

YOLOv9 exited with code 139 #906

trantuankhoi opened this issue Jan 8, 2025 · 2 comments
Labels
maybebug

Comments

@trantuankhoi
Copy link

First, I want to thank you for your excellent work.
I have successfully tested several samples serving the YOLO model and they worked perfectly. However, when I replaced the provided model with my custom YOLOv9 model, the pipeline was interrupted with exited code 139.
I have looked into similar issues (such as #882) and tried reverting to v0.4.9 or v0.4.2, but the issue persists. I have also searched for solutions in your Discord channel, but none of them helped.
Could you please help me identify what might be causing this issue or suggest any potential solutions?
Thank you for your time

module-1          |  INFO  insight::savant::savant_rs_video_decode_bin          > Adding branch with source cam1. First frame ID: 1. Caps: video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1280, height=(int)720, framerate=(fraction)30/1
module-1          |  INFO  insight::savant::savant_rs_video_decode_bin          > Branch with source cam1 added
module-1          |  INFO  insight::savant::savant_rs_video_demux               > Created new src pad for source cam1: src_cam1_1.
module-1          |  INFO  insight::savant::demo                                > Added source cam1
module-1          | max_fps_dur 3.33333e 07 min_fps_dur 3.33333e 07
module-1 exited with code 139
@bwsw bwsw added the maybebug label Jan 8, 2025
@bwsw
Copy link
Contributor

bwsw commented Jan 8, 2025

Hi, depending on YOLOv9 implementation, the bugs can occur in pre or post-processing code. Please provide us with the code to reproduce the problem.

@trantuankhoi
Copy link
Author

Oh, I sincerely apologize. I was naive in assuming that the output formats of YOLOv8 and YOLOv9 were the same, so I wouldn't need to worry about the post-processing.
After updating the post-processing, I've managed to fix this issue.
I'll close this issue and leave my code here for any lost souls who needs it.
Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
maybebug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bwsw @trantuankhoi