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

1.3.1 - 1.3.3 memory deallocation behaviour #800

Closed
theceday opened this issue Oct 2, 2017 · 2 comments
Closed

1.3.1 - 1.3.3 memory deallocation behaviour #800

theceday opened this issue Oct 2, 2017 · 2 comments

Comments

@theceday
Copy link

theceday commented Oct 2, 2017

I am really a beginner with opencv.
However there is strange behaviour change between versions
Not sure this is a bug though.

Mat contour = drawContour..

This is an actually unused variable and is drawed with actual image size. (not contour bounding box etc)
(image size 1600, 1200)

Same image, approx 6K contour.

1.3.1 keeping memory size around 150-200MB
1.3.3 after allocating 14GB memory, it crashes.

and this is replicable, happens everytime.
(same JDK, debug mode, no optimization etc)

Calling deallocate fixes the issue.

I really dont know whats the issue and whats could be changed, since Java doesnt have any way to deallocate scope variables?

@theceday
Copy link
Author

theceday commented Oct 2, 2017

maybe escape analysis doesnt work somehow?

@theceday theceday closed this as completed Oct 2, 2017
@saudet
Copy link
Member

saudet commented Oct 2, 2017 via email

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