When I try to run matplotlib/tests.py on master, linux, python 2.7, in a virtual machine with 4GB, the memory use grows out of control. Just running the test_axes chews up 1.5 G. Has anyone else seen this?
Eric
When I try to run matplotlib/tests.py on master, linux, python 2.7, in a virtual machine with 4GB, the memory use grows out of control. Just running the test_axes chews up 1.5 G. Has anyone else seen this?
Eric
I can confirm that after running the test suite with matplotlib.test() on a OSX 10.9 machine I end up with using around 1.5 Gb of memory. Furthermore the Python console that the tests are running from is extremely slow after the tests. Doing a gc.collect() frees most of the memory and returns the console to normal. I have only tested this with the stable 1.3.1 release
/Jens
On Sun, May 4, 2014 at 9:38 PM, Eric Firing <efiring@…272…229…> wrote:
When I try to run matplotlib/tests.py on master, linux, python 2.7, in a
virtual machine with 4GB, the memory use grows out of control. Just
running the test_axes chews up 1.5 G. Has anyone else seen this?
Eric
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
This is probably related to some of the random 'out of memory' errors
we have been getting on travis.
Maybe we should add `gc.collect` to the clean up method?
On Mon, May 5, 2014 at 7:15 AM, Jens Nielsen <jenshnielsen@...149...> wrote:
I can confirm that after running the test suite with matplotlib.test() on a
OSX 10.9 machine I end up with using around 1.5 Gb of memory. Furthermore
the Python console that the tests are running from is extremely slow after
the tests. Doing a gc.collect() frees most of the memory and returns the
console to normal. I have only tested this with the stable 1.3.1 release/Jens
On Sun, May 4, 2014 at 9:38 PM, Eric Firing <efiring@...229...> wrote:
When I try to run matplotlib/tests.py on master, linux, python 2.7, in a
virtual machine with 4GB, the memory use grows out of control. Just
running the test_axes chews up 1.5 G. Has anyone else seen this?Eric
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform
available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
matplotlib-devel List Signup and Options------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
matplotlib-devel List Signup and Options
--
Thomas Caswell
tcaswell@...149...