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.

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

EXC_BAD_ACCESS crash when running app with YOLOv3-SPP model trained on custom data. #17

Open
fellowProgrammer opened this issue Jan 9, 2020 · 5 comments

Comments

@fellowProgrammer
Copy link

I trained a YOLOv3-SPP model using custom data, I have 3 classes. I then converted it to a Keras .h5 file and then converted it to a CoreML. I ended up with a CoreML model whose Prediction section looks like this.

Screen Shot 2020-01-08 at 6 09 29 PM

I tried to use the app by adding the model to Xcode and changing the numClasses variable to 3, yet I still get this crash.

Screen Shot 2020-01-08 at 6 13 00 PM

I am quite new to the CoreML world so I don't have a good grasp on what info the MLMultiArrays hold and how to access it etc. What can I do to solve this crash? Is there something wrong with my model or is it just the app?

@andriikrupka
Copy link

andriikrupka commented Mar 24, 2020

Any updates? Have the same issue

@tj16kimura
Copy link

Me too.
Are there any solutions????

@tj16kimura
Copy link

I solved this problem by replacing

    for i in 0..<3 {  
            featurePointer = UnsafeMutablePointer<Double>(OpaquePointer(features[i].dataPointer))
            channelStride = features[i].strides[0].intValue
            yStride = features[i].strides[1].intValue
            xStride = features[i].strides[2].intValue

to

    for i in 0..<3 {  
            featurePointer = UnsafeMutablePointer<Double>(OpaquePointer(features[i].dataPointer))
            channelStride = features[i].strides[2].intValue
            yStride = features[i].strides[3].intValue
            xStride = features[i].strides[4].intValue

thanks

@andriikrupka
Copy link

@tj16kimura How did you find that? It's not so obvious

@tj16kimura
Copy link

@tj16kimura How did you find that? It's not so obvious

I checked the shape of features and found it was not correct.
I think it's because of Xcode's version.

sorry for my cheap English :<

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

3 participants