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 Leak #11

Open
pripyat opened this issue Dec 2, 2011 · 3 comments
Open

Memory Leak #11

pripyat opened this issue Dec 2, 2011 · 3 comments

Comments

@pripyat
Copy link

pripyat commented Dec 2, 2011

According to Instruments, there's a memory leak in - (BOOL)open. It specifically points to:

int err = sqlite3_open([databasePath fileSystemRepresentation], &handle);

If used frequently, this has a horrendous effect on RAM usage. Please fix! :)

@gradha
Copy link

gradha commented Dec 2, 2011

How do you suggest to fix that line? Opening a database might be a leak if you don't close it when you are finished with it.

@pripyat
Copy link
Author

pripyat commented Dec 2, 2011

The leak persists even if closed. I haven't studied the sqlite.c code as I can only do ObjC, sorry :/

@gradha
Copy link

gradha commented Dec 3, 2011

That's a weird way to put it, since ObjC is a superset of C and it's people who only know C who can't grok Objc.

Anyway, sqlite comes from the SDK, so there's not much egodatabase can do if the leak comes from sqlite itself and you should file a bug report against Apple (https://bugreport.apple.com/). Unless you are rolling your own sqlite version, in which case you should report the bug to the sqlite guys directly (http://www.sqlite.org/).

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