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 leaks in trackEvent #668

Closed
JordyFri opened this issue Jul 19, 2023 · 6 comments
Closed

Memory leaks in trackEvent #668

JordyFri opened this issue Jul 19, 2023 · 6 comments

Comments

@JordyFri
Copy link

Hello,

In order to have an application 100% memory leaks free we monitor our application constantly, we notice that our application is having memory issues just after sending a trackEvent with Adjust SDK,

we are sending a trackEvent as the documentation says, for example:
Screenshot 2023-07-19 at 11 46 17

and we got the memory issue (always when you call the trackEvent, new memory leaks are created):
Screenshot 2023-07-19 at 11 39 47

Any options o suggestions to solve this memory issue?

@uerceg
Copy link
Contributor

uerceg commented Jul 19, 2023

Hi @JordyFri,

Thank you for reporting this, we will check this on our end and keep you posted. Just to double check - which iOS SDK version is that you are experiencing this with?

@JordyFri
Copy link
Author

Hey @uerceg we are using the Adjust SDK v4.33.5

@uerceg
Copy link
Contributor

uerceg commented Jul 19, 2023

Thank you. We'll investigate this and will ping in here as soon as we have some update.

@uerceg uerceg mentioned this issue Jul 25, 2023
@uerceg
Copy link
Contributor

uerceg commented Jul 25, 2023

Hi @JordyFri,

We have just shipped the v4.33.6 release where we tried to address this issue. If you can give it a shot and let us know if you might still be facing this issue on your end, that would be great.

Looking forward to hearing back from you.

Cheers

@JordyFri
Copy link
Author

@uerceg Thanks so much for the support, it looks like the issue go away with the last version.

@uerceg
Copy link
Contributor

uerceg commented Jul 26, 2023

Amazing, thank you very much for the update. I'll close this ticket, but in case you still spot the issue later down the road, feel free to comment / reopen. Cheers!

@uerceg uerceg closed this as completed Jul 26, 2023
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