<br>On my box, the latest batch of refleak fixes seems to have fixed all but one of the leaky tests. test_threading_local still leaks, but it leaks rather consistently now (which is new.) I'm not able to make the other ones leak with any combination of '-u<resource>' or removing .pyc's beforehand or running longer or shorter. I hope it's not just my box :-)
<br><br>test_threading_local is not entirely consistent, but it looks a lot more reliable on my box than on Neal's automated mails:<br><br>test_threading_local<br>beginning 11 repetitions<br>12345678901<br>...........<br>
test_threading_local leaked [34, 34, 34, 34, 34, 26, 26, 22, 34] references<br><br>One remaining issue with refleakhunting on my machine is that test_tcl can't stand being run twice. Even without -R, this makes Python hang while waiting for a mutex in the second run through test_tcl:
<br><br>...trunk $ ./python -E -tt Lib/test/regrtest test_tcl test_tcl<br><br>Attaching gdb to the hung process shows this unenlightening trace:<br>#0 0x00002b7d6629514b in __lll_mutex_lock_wait () from /lib/libpthread.so.0
<br>#1 0x00002b7d6639a280 in completed.4801 () from /lib/libpthread.so.0<br>#2 0x0000000000000004 in ?? ()<br>#3 0x00002b7d66291dca in pthread_mutex_lock () from /lib/libpthread.so.0<br>#4 0x0000000000000000 in ?? ()<br>
<br>The process has one other thread, which is stuck here:<br>#0 0x00002b7d667f14d6 in __select_nocancel () from /lib/libc.so.6<br>#1 0x00002b7d67512d8c in Tcl_WaitForEvent () from /usr/lib/libtcl8.4.so.0<br>#2 0x00002b7d66290b1c in start_thread () from /lib/libpthread.so.0
<br>#3 0x00002b7d667f8962 in clone () from /lib/libc.so.6<br>#4 0x0000000000000000 in ?? ()<br><br>It smells like test_tcl or Tkinter is doing something wrong with regards to threads. I can reproduce this on a few machines, but all of them run newish linux kernels with newish glibc's and newish tcl/tk. At least in kernel/libc land, various thread related things changed of late. I don't have access to other machines with tcl/tk right now, but I wonder if anyone can reproduce this in different situations.
<br><br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!