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.

classification
Title: Error while sending function code over queue (multiprocessing)
Type: behavior Stage:
Components: Build Versions: Python 3.3
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: Filip.Malczak, davin
Priority: normal Keywords:

Created on 2013-12-15 16:39 by Filip.Malczak, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
pythonbug.txt Filip.Malczak, 2013-12-15 16:38
Messages (3)
msg206239 - (view) Author: Filip Malczak (Filip.Malczak) Date: 2013-12-15 16:38
Ive been using YAPSY to load plugins in one process. In this process I tried to put them in queue, and in another process I read them from queue.

There was a problem with non-existing type of plugin in consumer process, so I tried to serialize plugin instance by hand and deserialize by hand in consumer.

Both processes were created and started from main process, which passed them both the same queue.

Law forbids me from showing the whole code, but I'm attaching file with code pieces that generate error below:

Process ConsumerProcess-2:
Traceback (most recent call last):
  File "/usr/lib/python3.3/multiprocessing/process.py", line 258, in _bootstrap
    self.run()
  File "/usr/lib/python3.3/multiprocessing/process.py", line 95, in run
    self._target(*self._args, **self._kwargs)
  File "/<private_path>/consumer_stub.py", line 27, in _consumer
    result = foo()
  File "/<private_path>/loader_process.py", line 90, in x
    val = (kind, plugin, meta)
SystemError: ../Objects/cellobject.c:24: bad argument to internal function
msg237537 - (view) Author: Davin Potts (davin) * (Python committer) Date: 2015-03-08 15:02
While the mockup of the code that you provided is of some help, it is still unclear whether the problem could originate from your hand-rolled serialization/de-serialization implementation or somewhere else.  The traceback you shared could even suggest an unrelated problem in your project's code.  Without more information or, ideally, a runnable example of the problem that can be shared, there does not appear to be a way to take this forward.

Can more information be shared or a more complete example triggering the described behavior?
msg244426 - (view) Author: Davin Potts (davin) * (Python committer) Date: 2015-05-29 22:32
Without further information from the OP, there is not much more we can do as the problem may well originate with the user's compiled C code (which circumstantially seems quite likely).  Closing as out-of-date.
History
Date User Action Args
2022-04-11 14:57:55adminsetgithub: 64188
2015-05-29 22:32:07davinsetstatus: pending -> closed
resolution: out of date
messages: + msg244426
2015-03-08 15:02:51davinsetstatus: open -> pending

nosy: + davin
messages: + msg237537

type: crash -> behavior
2013-12-15 16:39:00Filip.Malczakcreate