Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Patrik H.
10 years agoExplorer | Level 4
Memory leak in SDK 1.3.13 (iOS and OSX)
Hi Dropboxers,
There seems to be a memory leak in the current SDK (1.3.13) for iOS and OSX. The issue is that DBRequest objects are not actually removed from the mutable set requests when a call to /revisions finishes. Specifically, it looks like there ought to be the following line
[requests removeObject:request];
at the end of requestDidLoadRevisions. The same problem seems to apply to requestDidRestoreFile. Can you confirm that my reading of the code is correct and this is indeed a memory leak, and the fix is that which I've described above?
Thanks!
Patrik
4 Replies
Replies have been turned off for this discussion
- Greg-DB10 years ago
Dropbox Community Moderator
Your reading looks right to me, so I'll report this to the team to check and fix it.
- Patrik H.10 years agoExplorer | Level 4
Thanks Gregory.
Actually it seems like there may also be other memory leaks: Making repeated calls to the API using the SDK (even with the provided example app) seems to grow the memory use of the app. Not by very much, but a little bit each time. So if the team is looking at this issue, might as well try to fix all the problems at the same time. I'll obviously report more on this thread if I happen to see what the problem might be.
Cheers,
Patrik
- Greg-DB10 years ago
Dropbox Community Moderator
Thanks! I'm adding that to the report as well.
- Greg-DB9 years ago
Dropbox Community Moderator
This should be addressed in release v1.3.14:
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!