Possible memory leak

[lucaippo]

Hi,
we noticed a memory leak on some of our applications using sqlany-django.
After some research we found that the number of instances of sqlanydb.Root was steadily increasing at each request.
sqlanydb.Root has indeed his desctructor registered within atexit (this should prevent correct garbage-collection), but sqlanydb only uses it "class-level cached" inside Connection, while sqlany-django instantiates it directly.
Are you aware of this behaviour or am I missing something?

The problem can be reproduced using latest version of sqlany-django (1.13) and Django 1.8, and repeatedly calling a view that uses sqlany_django database backend.
Either using django.db.models.Model or django.db.connection to interact with Sybase will do: memory used by the Django server process should increase by some Kbs per request, going up to several hundreds Mbs.

While we are at it, do you still actively support this project? It seems that latest issues and PRs are not getting much attention, and latest Django version supported is 1.8, which support ended April 1 2018.

[faxioman]

@gperrow it’s worth noting that this driver is linked from the official django documentation.
If this driver has memory leak and it’s in abandoned status I think it’s better to ask the django guys to remove sap sqlanywhere from the community supported dbs list.

[faxioman]

cc @gperrow-SAP

[gperrow-SAP]

My apologies for the delay in responding and for the neglect of the Django driver. There's been some rearranging of teams here and this driver seems to have gotten lost in the shuffle. I will make sure these issues get addressed.

[lucaippo]

Hi @gperrow-SAP, any news on this?

[WaYdotNET]

Hi @gperrow-SAP, any news on this?

[faxioman]

@lucaippo @WaYdotNET @gperrow-SAP
This is the ticket where I asked to remove SAP SQL Anywhere from the "3rd party database backend" page.
https://code.djangoproject.com/ticket/30169