➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2010-01-31 23:48 by vstinner, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| issue7825_test_threadsignals.diff | flox, 2010-03-04 12:27 | Patch, apply to 2.x | ||
| Messages (7) | |||
|---|---|---|---|
| msg98636 - (view) | Author: STINNER Victor (vstinner) *  |
Date: 2010-01-31 23:48 | |
test_threadsignals leaks references. I'm unable to understand where. Maybe somewhere around Py_AddPendingCall()? --------- $ ./python Lib/test/regrtest.py -R 3:2: test_threadsignals test_threadsignals beginning 5 repetitions 12345 ..... test_threadsignals leaked [8, 8] references, sum=16 1 test failed: test_threadsignals --------- |
|||
| msg100384 - (view) | Author: Florent Xicluna (flox) * |
Date: 2010-03-04 12:27 | |
A way to fix the transient leaks. |
|||
| msg110936 - (view) | Author: Mark Lawrence (BreamoreBoy) * | Date: 2010-07-20 17:54 | |
Has the underlying code been fixed or could we still use the patch to test_threadsignals? |
|||
| msg111492 - (view) | Author: Mark Lawrence (BreamoreBoy) * | Date: 2010-07-24 16:26 | |
The patch is small and easily applied, but no point me trying it as I've only a Windows box. Also note that my earlier comment was incorrect as I misread the original post. |
|||
| msg111729 - (view) | Author: Florent Xicluna (flox) * |
Date: 2010-07-27 20:48 | |
I did not commit the patch because I'm not sure it is the right approach. I need someone else to comment on this. |
|||
| msg111744 - (view) | Author: Antoine Pitrou (pitrou) * |
Date: 2010-07-27 22:43 | |
I haven't seen test_threadsignals leaking, either on 3.1 or 3.2. Was it a transient problem? Note that if you want for test-specific threads to end, you can use the reap_threads() utility from the test.support module. |
|||
| msg111746 - (view) | Author: Florent Xicluna (flox) * |
Date: 2010-07-27 22:51 | |
Now it's fixed for 2.7 with r83187. (thanks for the hint, Antoine) No issue on 3.x, AFAICT. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:57 | admin | set | github: 52073 |
| 2010-07-27 22:51:19 | flox | set | status: open -> closed resolution: fixed messages: + msg111746 stage: patch review -> resolved |
| 2010-07-27 22:43:12 | pitrou | set | nosy:
+ pitrou messages: + msg111744 |
| 2010-07-27 20:48:10 | flox | set | messages: + msg111729 |
| 2010-07-24 16:26:42 | BreamoreBoy | set | messages: + msg111492 |
| 2010-07-20 17:54:06 | BreamoreBoy | set | nosy:
+ BreamoreBoy messages: + msg110936 |
| 2010-03-04 12:28:00 | flox | set | files:
+ issue7825_test_threadsignals.diff priority: normal keywords: + patch nosy: + flox messages: + msg100384 stage: patch review |
| 2010-01-31 23:48:22 | vstinner | create | |