Closed afonsomartingo closed 2 months ago
Hi @afonsomartingo , could you please confirm whether the suggested fix to your question on the forums resolves your issue?
Hi, I don't know if this problem was resolved because this was only happening with AJA source, as I'm trying to use RDMA for the purpose of doing Keyer, AJA gave me the new drivers and now I'm dealing with this problem:
https://forums.developer.nvidia.com/t/holoscan-video-output-via-aja-capture-card-using-keyer/301973
Therefore, at this moment AJA is not configured correctly, so that I cant check whether the previous problem has been resolved or not. But when I fix it I'll check.
Thanks
Tom Birdsong @.***> escreveu (quinta, 1/08/2024 à(s) 16:35):
Hi @afonsomartingo https://github.com/afonsomartingo , could you please confirm whether the suggested fix to your question on the forums https://forums.developer.nvidia.com/t/cudaruntimeerror-cudaerrorillegaladdress-an-illegal-memory-access-was-encountered/296973 resolves your issue?
— Reply to this email directly, view it on GitHub https://github.com/nvidia-holoscan/holoscan-sdk/issues/31#issuecomment-2263371827, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASVFCYMYG7QIM524FTWHPYTZPJISXAVCNFSM6AAAAABLMRD7EKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGM3TCOBSG4 . You are receiving this because you were mentioned.Message ID: @.***>
Hi @afonsomartingo , can you please confirm if updating to a later Holoscan SDK version resolves your issue as suggested in the forum response here? The latest release of Holoscan SDK is v2.3.0, it looks like you are using v2.1.0.
Hi Tom, sorry I haven't been able to check yet. When I do, I'll give you some feedback.
Best regards
Tom Birdsong @.***> escreveu (sexta, 16/08/2024 à(s) 18:28):
Hi @afonsomartingo https://github.com/afonsomartingo , can you please confirm if updating to a later Holoscan SDK version resolves your issue as suggested in the forum response here https://forums.developer.nvidia.com/t/cudaruntimeerror-cudaerrorillegaladdress-an-illegal-memory-access-was-encountered/296973? The latest release of Holoscan SDK is v2.3.0, it looks like you are using v2.1.0.
— Reply to this email directly, view it on GitHub https://github.com/nvidia-holoscan/holoscan-sdk/issues/31#issuecomment-2293887484, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASVFCYKQFDNYC44RG7UKHTDZRYZC5AVCNFSM6AAAAABLMRD7EKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJTHA4DONBYGQ . You are receiving this because you were mentioned.Message ID: @.***>
Hi @afonsomartingo , moving to close this issue as stale. The original issue has been addressed in Holoscan SDK v2.2, please try testing with that version when you can and re-open this ticket if the problem persists.
Hi Tom, ok thanks for the update. I will do that.
Best regards
A terça, 10/09/2024, 16:44, Tom Birdsong @.***> escreveu:
Hi @afonsomartingo https://github.com/afonsomartingo , moving to close this issue as stale. The original issue has been addressed in Holoscan SDK v2.2 https://forums.developer.nvidia.com/t/cudaruntimeerror-cudaerrorillegaladdress-an-illegal-memory-access-was-encountered/296973, please try testing with that version when you can and re-open this ticket if the problem persists.
— Reply to this email directly, view it on GitHub https://github.com/nvidia-holoscan/holoscan-sdk/issues/31#issuecomment-2341307072, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASVFCYJBQ6P7QX6KLPM4RXTZV4HV3AVCNFSM6AAAAABLMRD7EKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGMYDOMBXGI . You are receiving this because you were mentioned.Message ID: @.***>
Dear devs,
I recently updated the Holoscan SDK from the older v1.0.3 to the v2.1.0. My application was running on the older SDK and after update the app stoped working. It runs with a video file with this path (Path 1: replayer,ImageProcessing,preprocessor,inference,postprocessor,PostImageProcessing,viz) but when i try to run it with a video feed from AJA source operator the app shows this error. This error appears exactly when i try to preprocess the frame, but only happens using AJA not using replayer. I checked the new release notes and noticed that the update changed the way FormatConverterOp operates on host/device copies. I use Cupy to acquire the frame that was sent through a Tensor Holoscan, I think the error I am facing is related to Cupy waiting for data on the GPU and after the update this change of FormatConverterOp automatically performs a copy of the host->device could be the problem. What can I do to fix this?
Logs
My code (Compute method)