multiprocessing generates a fatal error

[brianquinlan]

BPO	10632
Nosy	@brianquinlan, @orsenthil, @pitrou, @davidmalcolm, @sandrotosi
Superseder	bpo-10632: multiprocessing generates a fatal error

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2011-04-27.17:11:18.861>
created_at = <Date 2010-12-05.18:53:49.961>
labels = ['library', 'type-crash']
title = 'multiprocessing generates a fatal error'
updated_at = <Date 2011-04-27.17:16:34.274>
user = 'https://github.com/brianquinlan'

bugs.python.org fields:

activity = <Date 2011-04-27.17:16:34.274>
actor = 'pitrou'
assignee = 'jnoller'
closed = True
closed_date = <Date 2011-04-27.17:11:18.861>
closer = 'jnoller'
components = ['Library (Lib)']
creation = <Date 2010-12-05.18:53:49.961>
creator = 'bquinlan'
dependencies = []
files = []
hgrepos = []
issue_num = 10632
keywords = []
message_count = 9.0
messages = ['123433', '132410', '132418', '132429', '132634', '132681', '132696', '134590', '134597']
nosy_count = 7.0
nosy_names = ['bquinlan', 'orsenthil', 'pitrou', 'jnoller', 'dmalcolm', 'sandro.tosi', 'neologix']
pr_nums = []
priority = 'high'
resolution = 'duplicate'
stage = 'needs patch'
status = 'closed'
superseder = '10632'
type = 'crash'
url = 'https://bugs.python.org/issue10632'
versions = ['Python 3.2']

[brianquinlan]

multiprocessing generates fatal error "Invalid thread state for this thread" in PyThreadState_Swap

This seems to happen on RHEL 5 and Centos 5.5

Here is the minimal repro:
>>> import multiprocessing.managers
>>> mpp = multiprocessing.Pool(4)
>>> sm = multiprocessing.managers.SyncManager()
>>> sm.start()

See http://bugs.python.org/issue10517 for more details

[sandrotosi]

Hi Brian,
are you able to replicate it? I just build 3.2 and default (3.3) on a Debian unstable system and wasn't able to replicate it (with a busy loop like while date ; do ./python -c "import multiprocessing.managers ; mpp = multiprocessing.Pool(4); sm = multiprocessing.managers.SyncManager(); sm.start()" ; done )

[brianquinlan]

No, I wasn't able to replicate.

[sandrotosi]

can we close this issue then?

[orsenthil]

I wonder if this is CentOS and RHEL specific. Unable to reproduce this on Ubuntu.

[davidmalcolm]

This is indeed looking like it's RHEL-specific.

I was about to close it out as a duplicate of bpo-10517, but I'm wondering why Brian chose to open it as a separate bug.

[brianquinlan]

Filing a new bug might have been a mistake. Once the investigation in bpo-10517 isolated the failure as being in a different module, I thought it best to file a new bug with a minimal repro case.

Fill free to cleanup.

[neologix]

It's a duplicate of http://bugs.python.org/issue10517

[jnoller]

Dupe of bpo-10517