[BUG]: OpenMP loops hang with Python virtual function overrides
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
Required prerequisites
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker and Discussions to verify that this hasn't already been reported. +1 or comment there if it has.
- Consider asking first in the Gitter chat room or in a Discussion.
What version (or hash if on master) of pybind11 are you using?
9b4f71d1
Problem description
I'm having a problem with pybind11 wrapped code using virtual function overrides in OpenMP sections of C++ code. An OpenMP loop will hang when run with more than one thread if there are calls to Python overrides in the body of the code. Since the macro PYBIND11_OVERRIDE acquires the GIL I thought these sorts of operations should be safe, but clearly I'm missing something.
I've looked through the issues and discussions, but I don't see the solution for this problem. I've raised this as a Discussion at https://github.com/pybind/pybind11/discussions/5102 if that's a more appropriate place to examine this problem (like I'm making a mistake I don't see, certainly possible).
The C++ code block below will generate the problem when run with the Python code that follows.
Reproducible example code
#include "pybind11/pybind11.h"
#include "pybind11/functional.h"
namespace py = pybind11;
using namespace pybind11::literals;
#include <cstdio>
class A {
public:
A() { printf("A::A()\n"); }
virtual ~A() { printf("A::~A()\n"); }
virtual void void_func() const { printf("A::void_func()\n"); }
virtual int int_func(int x) const { printf("A::int_func(%d)\n", x); return x + 1; }
};
void do_threaded_stuff(const A& a) {
int sum = 0;
#pragma omp parallel for
for (auto i = 0u; i < 10u; ++i) {
a.void_func();
#pragma omp critical
{
sum = a.int_func(sum);
}
}
printf("Final sum: %d\n", sum);
}
//------------------------------------------------------------------------------
// Trampoline class for A
//------------------------------------------------------------------------------
class PYB11TrampolineA: public A {
public:
using A::A;
virtual void void_func() const override {
PYBIND11_OVERRIDE(void, A, void_func);
}
virtual int int_func(int x) const override {
PYBIND11_OVERRIDE(int, A, int_func, x);
}
};
//------------------------------------------------------------------------------
// Make the module
//------------------------------------------------------------------------------
PYBIND11_MODULE(virtual_override_thread, m) {
py::class_<A, PYB11TrampolineA> obj(m, "A");
obj.def(py::init<>());
obj.def("void_func", (void (A::*)() const) &A::void_func);
obj.def("int_func", (int (A::*)(int) const) &A::int_func);
m.def("do_threaded_stuff", (void (*)(const A&)) &do_threaded_stuff, "a"_a);
}
# Python reproducer
from virtual_override_thread import *
class B(A):
def __init__(self):
A.__init__(self)
def void_func(self):
print("B::void_func")
def int_func(self, x):
print("B::int_func({})".format(x))
return x + 10
a = A()
do_threaded_stuff(a) # OK
b = B()
do_threaded_stuff(b) # Hang with OMP_NUM_THREADS > 1
Is this a regression? Put the last known working version here if it is.
Not a regression
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied C++ and Python reproducer, focusing on the PYBIND11_OVERRIDE calls inside the OpenMP loop and how they interact with the GIL. Run it with OMP_NUM_THREADS greater than one, then inspect the relevant override and threading documentation or implementation. Done means the reproducer no longer hangs while Python virtual overrides remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100