Kåre Krig <karek...@gmail.com> added the comment:

I managed to get access to another two systems to test this on. One running 
ubuntu & python 2.7.1 and the other suse & python 2.6. I could not reproduce 
the bug on either of those systems.

This all points to the issue not really being a bug in python but something on 
my system.

The fact that I could predictably produce this bug using <20Mb of data, then 
pass 15 hours of memtest86+ and finally produce the bug again makes me think 
it's not the ram system, but there are of course layers between python and the 
ram that might be broken.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12784>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to