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

Memory #2

Open
Alukardo opened this issue Dec 27, 2018 · 4 comments
Open

Memory #2

Alukardo opened this issue Dec 27, 2018 · 4 comments

Comments

@Alukardo
Copy link

Thank you for sharing this model. But when I use Xcode to debug this Example, there will be a memory issue. Can you can help me?
memory issue 1
memory issue 2

@vadimux
Copy link

vadimux commented Feb 7, 2019

I have the same issue for devices like iPhone 6s and etc. But on iPad Pro there is no this crash (out of memory). I guess it's related to model.
upd. As I see, the issue is related to internal part of CoreML:
screen shot 2019-02-07 at 17 31 46

upd2: I've researched this crash and found the place of out of memory:
PyramidROIAlignLayer.swift L.116 after comment

//This is the main bottleneck. Is there a more efficient approach?

@deandiakov
Copy link

I have the same issue for devices like iPhone 6s and etc. But on iPad Pro there is no this crash (out of memory). I guess it's related to model.
upd. As I see, the issue is related to internal part of CoreML:
screen shot 2019-02-07 at 17 31 46

upd2: I've researched this crash and found the place of out of memory:
PyramidROIAlignLayer.swift L.116 after comment

//This is the main bottleneck. Is there a more efficient approach?

Did you ever figure out a workaround to the memory issue? Also, what iPad model and iOS version were you able to make it work on? I'm currently struggling to get the debugger working even on my First Gen iPad Pro running iOS 12.1.1.

@vadimux
Copy link

vadimux commented Feb 11, 2019

@deandiakov right now i'm trying to find a workaround for this issue.
I use several devices and only on iPad Pro (ML0G2CL/A) with iOS 12.1 (16B92) there is no this memory issue.

@vadimux
Copy link

vadimux commented Feb 18, 2019

@deandiakov
Unfortunately, I could not find a fix for this crash

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