You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, author, thank you for your code; it has significantly sped up my development process.
I encountered an issue during usage:
I downloaded yolov8s-seg.pt from the official YOLO repository and used the following code to convert it to ONNX format:
from ultralytics import YOLO
model = YOLO("yolov8s-seg.pt")
model.export(format="onnx")
Afterward, when running the following in C#:
var results = yolo.RunSegmentation(image, 0.25, 0.65, 0.7);
I encountered the error: System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'
However, if I use yolov8s-seg.onnx from YoloDotNet\test\assets\Models, there are no issues.
Out of curiosity and for learning purposes, I would like to know:
What is causing the error?
Is my method for converting yolov8s-seg.pt correct? If not, how can I correctly perform the conversion?
Looking forward to your response, thank you!
The text was updated successfully, but these errors were encountered:
Hello, author, thank you for your code; it has significantly sped up my development process.
I encountered an issue during usage:
I downloaded
yolov8s-seg.pt
from the official YOLO repository and used the following code to convert it to ONNX format:Afterward, when running the following in C#:
I encountered the error:
System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'
However, if I use
yolov8s-seg.onnx
fromYoloDotNet\test\assets\Models
, there are no issues.Out of curiosity and for learning purposes, I would like to know:
What is causing the error?
Is my method for converting
yolov8s-seg.pt
correct? If not, how can I correctly perform the conversion?Looking forward to your response, thank you!
The text was updated successfully, but these errors were encountered: