Skip to content

Access violation in object destruction after stopping pipeline. #43

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

Open
MaksimDanilov opened this issue Mar 10, 2025 · 3 comments
Open

Comments

@MaksimDanilov
Copy link

Describe the bug
After stopping pipeline sometimes I receive object access error. I simplified your examples (ob_point_cloud.exe) to catch that error. Just put to main exception handling and catch only one frames and then exit. Make object destruction before return statement. I guess pipeline received data after being stopped.

Reproduction Steps

  1. Run modified example (ob_point_cloud.exe) with debugger.
  2. Catch depth frame.
  3. Save to ply.
  4. Destroy pipeline.

Expected behavior
No frames received after pipeline destroyed.

Log Output
Include relevant log entries or error messages that are related to the problem.You can attach log files if they are too large.

System Environment:

  • OS: Windows 11
  • Architecture: x86_64
  • Visual Studio/GCC:Visual Studio 2022

Tool/SDK Version:

  • SDK: 2.2.8

Device Information:

  • Model: Microsoft Surface Pro 11.
  • Firmware Version: Firmware revision number.

Additional context

Image
@zhonghong322
Copy link
Contributor

Can you provide the modified test code you used?

@MaksimDanilov
Copy link
Author

MaksimDanilov commented Mar 19, 2025

Can you provide the modified test code you used?

Sorry. Somehow I missed the message. Sure. I'll past file tomorrow.

@MaksimDanilov
Copy link
Author

point_cloud.txt
@zhonghong322 Try this :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants