1ytic/warp-rnnt

runtime error with Python 3.8

funcwj opened this issue · 4 comments

funcwj commented

Recently I found this bindings can not work properly with Python 3.8 (no problems with Python 3.7). When running python -m warp_rnnt.test, the errors reported like:

======================================================================
ERROR: test_calls (__main__.RNNTLossTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/environment/jwu/miniconda3/envs/jwu/lib/python3.8/site-packages/warp_rnnt/test.py", line 204, in test_calls
    costs, grads = core.rnnt_loss(
RuntimeError: rnnt_loss status 1 (rnnt_loss at binding.cpp:110)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x47 (0x7fa92bd8e627 in /home/environment/jwu/miniconda3/envs/jwu/lib/python3.8/site-packages/torch/lib/libc10.so)
frame #1: rnnt_loss(at::Tensor const&, at::Tensor const&, at::Tensor const&, at::Tensor const&, int) + 0x214f (0x7fa911a86d3f in /home/environment/jwu/miniconda3/envs/jwu/lib/python3.8/site-packages/warp_rnnt/_C.cpython-38-x86_64-linux-gnu.so)
frame #2: <unknown function> + 0x23e02 (0x7fa911a99e02 in /home/environment/jwu/miniconda3/envs/jwu/lib/python3.8/site-packages/warp_rnnt/_C.cpython-38-x86_64-linux-gnu.so)
frame #3: <unknown function> + 0x241ee (0x7fa911a9a1ee in /home/environment/jwu/miniconda3/envs/jwu/lib/python3.8/site-packages/warp_rnnt/_C.cpython-38-x86_64-linux-gnu.so)
frame #4: <unknown function> + 0x218b6 (0x7fa911a978b6 in /home/environment/jwu/miniconda3/envs/jwu/lib/python3.8/site-packages/warp_rnnt/_C.cpython-38-x86_64-linux-gnu.so)
<omitting python frames>

The pytorch version is 1.4.0 and the CUDA version is 10.0.

funcwj commented

I guess it's pybind11's issues.

1ytic commented

@funcwj thanks for the issue, but I can not reproduce your error. I used python=3.8, pytorch=1.4.0, cudatookkit=10.0 and all tests ran successfully. Maybe the issue is indeed with pybind11. I use pybind11=2.5.0.

yuekaizhang commented

@funcwj， Do you fix the issue? I met the same problem with pybind11=2.5.0

harisgulzar1 commented

I faced this issue on Python3.7
Uninstalling warp-rnnt and reinstalling warp-rnnt 0.6.0 salved the issue.
pip uninstall warp-rnnt
pip install warp-rnnt==0.6.0

  • 👍2