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 issue #48

Open
shock-wave007 opened this issue Jun 9, 2018 · 11 comments
Open

Memory issue #48

shock-wave007 opened this issue Jun 9, 2018 · 11 comments
Labels
bug Something isn't working

Comments

@shock-wave007
Copy link

screenshot 24

if i change filter multiples time without "largerHeap="true" application crashes and as u can see in screenshot that it take upto 1.2Gb no phone, it some kind of memory leak or something.

@burhanrashid52
Copy link
Owner

We are using GLSurfaceView for image filtering which takes more resources to filter images. Thanks for the update I will look into it

@shock-wave007
Copy link
Author

Its ok if we apply 2-3 filter, but as we keep cycling through filters, memory keep increasing.

Setps to reproduce result
Run in ADV or device
Open resource monitor in Android studios
And change fliter

As u change it just keep consuming memory
The slope in memory graph

@kustraslawomir
Copy link

kustraslawomir commented Oct 23, 2018

@shock-wave007 @burhanrashid52

call GLES20.glDeleteTextures(2, mTextures, 0) before GLES20.glGenTextures(2, mTextures, 0) at loadTextures() method to resolve memory issue.

@IgorKlv
Copy link

IgorKlv commented Oct 29, 2018

@kustraslawomir I applied your solution, yet it has not helped to conserve memory and the App continually crashes after resuming filter selection.

@el-Knix
Copy link

el-Knix commented Jan 21, 2019

Hey there did anyone manage to find a solution to this issue?

@mohammad1ta
Copy link

Hi,
No solution? :(

I have this issue to, I submitted this problem in stackoverflow

@burhanrashid52 burhanrashid52 added the bug Something isn't working label Feb 19, 2019
@mohammad1ta
Copy link

@shock-wave007 @burhanrashid52

call GLES20.glDeleteTextures(2, mTextures, 0) before GLES20.glGenTextures(2, mTextures, 0) at loadTextures() method to resolve memory issue.

Thank you dear Kustra,
I tested your solution and helped me a few to control memory. ( after set filter, memory will be back to old step ).
But still its high memory usage...

@burhanrashid52
Copy link
Owner

The solution by @kustraslawomir worked @mohammad1ta ?

@mohammad1ta
Copy link

The solution by @kustraslawomir worked @mohammad1ta ?

Yes, at the first time, When I use filter, memory will grow up from about 130MB to 232MB ( Because Graphics memory 0MB to 96MB ).
after second changing in filter, memory increases to 260MB and decrease back to 235MB.

@wifirevaithi
Copy link

hi, Is there is any permanent Solution For this Problem..? @burhanrashid52 @kustraslawomir

@maximusapp
Copy link

maximusapp commented Mar 19, 2020

@shock-wave007 @burhanrashid52
call GLES20.glDeleteTextures(2, mTextures, 0) before GLES20.glGenTextures(2, mTextures, 0) at loadTextures() method to resolve memory issue.

Thank you dear Kustra,
I tested your solution and helped me a few to control memory. ( after set filter, memory will be back to old step ).
But still its high memory usage...

Your tip help me, but that its help me, you need export this project like module, not implement in gradle. Memory not increase but app still crash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants