-
Notifications
You must be signed in to change notification settings - Fork 187
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
Question: memory seems to be leaked #24
Comments
I seem to have the same issue. |
This was solved? I want use in our project :( |
Any news? |
Running into the same problem. Was debugging my app due to +100% CPU after transitioning away from a view controller with a PastelView. Tried removing, stopping, and weak referencing through an IBOutlet as well. |
Maybe it's a long not-touched thread, but I will try to fix it in one of the upcoming maintenance fixes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear Community,
Hello, I'm Masa. Pardon my stupid question.
I was trying Pastel with Memory Graph Debug, and it seemed to cause memory leak.
I also confirmed Passcode which used Pastel, and I confirmed same phenomenon.
(It seems to cause when initializing colors property and inside PastelView#currentGradientSet() method.)
I've been searching and thinking the reason and solution, but I've not found a solution yet...
(I found some articles which say objects included "core" framework originally aren't be located under ARC, so I suspect this relates to memory leak but I've not found a perfect solution.)
So, Can I use Pastel ignoring this phenomenon? Is that not a big problem?
I'm sorry to bother you.
Thanks,
Masa
The text was updated successfully, but these errors were encountered: