(Ubuntu 12.04 x64, native Python 2.7.3 x64, ObsPy 0.9.2)
When used in a long running program, ObsPy SeedLink client seems to leak memory. The leak
can be discovered with the low level tools like the ‘resource’ module:
somewhere in the SLClient callback…
For long running tasks, this displays ever increasing amount of memory used. While high-level
tools reporting the number of newly created Python objects like ObjGraph display nothing.
We believe the leak is due to the range() operator used in obspy/client/slstate.py, line 202.
We now use a patched version of the SeedLink client which employs xrange() function instead
of the range() operator. This seems to fix the leak.