Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6659487
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T02:02:26+00:00 2026-05-26T02:02:26+00:00

It seems that when an exception is raised from a multiprocessing.Pool process, there is

  • 0

It seems that when an exception is raised from a multiprocessing.Pool process, there is no stack trace or any other indication that it has failed. Example:

from multiprocessing import Pool 

def go():
    print(1)
    raise Exception()
    print(2)

p = Pool()
p.apply_async(go)
p.close()
p.join()

prints 1 and stops silently. Interestingly, raising a BaseException instead works. Is there any way to make the behavior for all exceptions the same as BaseException?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T02:02:26+00:00Added an answer on May 26, 2026 at 2:02 am

    I have a reasonable solution for the problem, at least for debugging purposes. I do not currently have a solution that will raise the exception back in the main processes. My first thought was to use a decorator, but you can only pickle functions defined at the top level of a module, so that’s right out.

    Instead, a simple wrapping class and a Pool subclass that uses this for apply_async (and hence apply). I’ll leave map_async as an exercise for the reader.

    import traceback
    from multiprocessing.pool import Pool
    import multiprocessing
    
    # Shortcut to multiprocessing's logger
    def error(msg, *args):
        return multiprocessing.get_logger().error(msg, *args)
    
    class LogExceptions(object):
        def __init__(self, callable):
            self.__callable = callable
    
        def __call__(self, *args, **kwargs):
            try:
                result = self.__callable(*args, **kwargs)
    
            except Exception as e:
                # Here we add some debugging help. If multiprocessing's
                # debugging is on, it will arrange to log the traceback
                error(traceback.format_exc())
                # Re-raise the original exception so the Pool worker can
                # clean up
                raise
    
            # It was fine, give a normal answer
            return result
    
    class LoggingPool(Pool):
        def apply_async(self, func, args=(), kwds={}, callback=None):
            return Pool.apply_async(self, LogExceptions(func), args, kwds, callback)
    
    def go():
        print(1)
        raise Exception()
        print(2)
    
    multiprocessing.log_to_stderr()
    p = LoggingPool(processes=1)
    
    p.apply_async(go)
    p.close()
    p.join()
    

    This gives me:

    1
    [ERROR/PoolWorker-1] Traceback (most recent call last):
      File "mpdebug.py", line 24, in __call__
        result = self.__callable(*args, **kwargs)
      File "mpdebug.py", line 44, in go
        raise Exception()
    Exception
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

It seems that this part of my code is where the exception occurs: c
I have an application that seems to throw exceptions only after the program has
[ Solved , it seems that there was some bug affecting Alfresco 3.3.0, which
I have some extremely weird behavior that seems to result in silent exceptions. How
In one of our application im getting an exception that i can not seem
Seems that requirements on safety do not seem to like systems that use AI
Seems that even after unchecking the option in the PyDev/Debug preferenecs pane to launch
It seems that a List object cannot be stored in a List variable in
It seems that it is impossible to capture the keyboard event normally used for
It seems that Silverlight/WPF are the long term future for user interface development with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.