Importing opencv fails with "ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in static TLS block"

[emdioh]

Environment data

• debugpy version: 1.0.0b12
• OS and version: Ubuntu 20.04.1 LTS
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.8.2 - coming with the distro
• Python3-Opencv version: 4.2.0+dfsg-5
• Using VS Code or Visual Studio: VS Code

Actual behavior

Debugging scripts that import opencv2 fail to run at "import cv2" statement

$python -m debugpy --listen 1234 -c "import cv2"

Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 193, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/yolo/.local/lib/python3.8/site-packages/debugpy/__main__.py", line 45, in <module>
    cli.main()
  File "/home/yolo/.local/lib/python3.8/site-packages/debugpy/server/cli.py", line 430, in main
    run()
  File "/home/yolo/.local/lib/python3.8/site-packages/debugpy/server/cli.py", line 330, in run_code
    eval(code, {})
  File "<string>", line 1, in <module>
ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in static TLS block

Expected behavior

Import succeeds, the script can run under the debugger.

Steps to reproduce:

1. install debugpy 1.0.0b12
2. python -m debugpy --listen 1234 -c "import cv2"

Notes

Version 1.0.0b11 works.

[int19h]

This sounds like https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1890170 - from the various reports there, it looks like cv2 might have some conflicts with other packages employing native code?

[fabioz]

Since it works with a previous version and not this one, this may be the same thing as:

#356

where the environment variables in the launch appear to be different from one launch to the other due to an upgrade.

@emdioh can you run the script below in 1.0.0.b11 and 1.0.0.b12 and check if the environment variables are different from one case to the other?

import sys
print(sys.version)

import os
for key, val in sorted(os.environ.items()):
    print(key)
    for v in val.split(os.pathsep):
        print('    %s' % v)  

print('\nsys.path:')
for v in sys.path:
    print('    %s' % (v,)) 
print('\n')

[emdioh]

I can't see any diff in the environment variables. In the mean time, debugpy 1.0.0rc2 is out and the issue went away

…

On Fri, Aug 21, 2020 at 8:05 PM Fabio Zadrozny ***@***.***> wrote: Since it works with a previous version and not this one, this may be the same thing as: #356 <#356> where the environment variables in the launch appear to be different from one launch to the other due to an upgrade. @emdioh <https://github.com/emdioh> can you run the script below in 1.0.0.b11 and 1.0.0.b12 and check if the environment variables are different from one case to the other? import sys print(sys.version) import os for key, val in sorted(os.environ.items()): print(key) for v in val.split(os.pathsep): print(' %s' % v) print('\nsys.path:') for v in sys.path: print(' %s' % (v,)) print('\n') — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#350 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWDZGDJD5W6YSAV4C2VI53SB2ZPXANCNFSM4PLK7D2A> .

[int19h]

Sounds like we accidentally fixed it.