-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sentencepiece==0.1.92
seems breaking something
#505
Comments
Thank you. I cannot reproduce this error. Can you take the stack trace or result of strace? I will temporarlly disable 0.19.2 release just in case. Thank you |
Downgraded. |
Thanks for your prompt action. (env) xug@XUG:~$ python -c "import transformers,torch; torch.rand(3)"
(env) xug@XUG:~$ pip install sentencepiece==0.1.92
WARNING: The candidate selected for download or install is a yanked version: 'sentencepiece' candidate (version 0.1.92 at https://files.pythonhosted.org/packages/68/e5/0366f50a00db181f4b7f3bdc408fc7c4177657f5bf45cb799b79fb4ce15c/sentencepiece-0.1.92-cp36-cp36m-manylinux1_x86_64.whl#sha256=7fd16c761339f593596b63e50810a2d2eff964d428ab79a49674c7371c055561 (from https://pypi.org/simple/sentencepiece/))
Reason for being yanked: Crash bug is reported (confirming)
Collecting sentencepiece==0.1.92
Using cached sentencepiece-0.1.92-cp36-cp36m-manylinux1_x86_64.whl (1.2 MB)
Installing collected packages: sentencepiece
Attempting uninstall: sentencepiece
Found existing installation: sentencepiece 0.1.91
Uninstalling sentencepiece-0.1.91:
Successfully uninstalled sentencepiece-0.1.91
Successfully installed sentencepiece-0.1.92
(env) xug@XUG:~$ python -c "import transformers,torch; torch.rand(3)"
Segmentation fault (core dumped) Last time I see a similar issue in scipy/scipy#11237. |
0.1.92 is also causing segfaults for me during training. (Haven't had time to track down the exact line) |
+1 |
I can confirm, I have been having the exact same issue with version 0.1.92 which I don't with 0.1.91. Current thread 0x00007fa347061280 (most recent call first):
File ".../lib/python3.7/site-packages/torch/nn/modules/module.py", line 74 in __init__
File ".../lib/python3.7/site-packages/torch/nn/modules/loss.py", line 10 in __init__
File ".../lib/python3.7/site-packages/torch/nn/modules/loss.py", line 593 in __init__ That line happens to be: torch._C._log_api_usage_once("python.nn_module") I suspect something in the sentencepiece new version prevent torch binaries from normally register its resources. Downgrading to version 0.1.91 fixes the issue for me as well. |
I'm also seeing segfault. Here is gdb output if that helps gist. |
Thank you for the investigation. We've upgraded internal protobuf version in 0.19.2. Not sure the root cause, but I beleve that this causes the crash. I wil rollback this protobuf version and release 0.19.3 soon. |
I had this issue while building tensorflow-text from source, i tried to build mainly to see what was breaking with sentencepiece, proto buffer versions seems to be messing up. ERROR: /home/XXXX/Downloads/text/tensorflow_text/core/kernels/BUILD:310:18: C++ compilation of rule '//tensorflow_text/core/kernels:sentencepiece_kernels' failed (Exit 1) |
Seems that protobuf is not a root cause. The error persits after downloading protobuf.
|
Is it the same as pytorch/pytorch#8358? This looks like another case of incompatibility with PyTorch which releases non standard Sometimes the import order helps working around the issue:
|
I am not using PyTorch. Built Tensorflow from source for Cuda 11. And tried
building tensorflow_text.
…On Thu, Jun 18, 2020 at 4:46 AM Guillaume Klein ***@***.***> wrote:
Is it the same as pytorch/pytorch#8358
<pytorch/pytorch#8358>? This looks like another
case of incompatibility with PyTorch which releases non standard
manylinux1 packages, not SentencePiece fault.
Sometimes the import order helps working around the issue:
$ python
>>> import torch
>>> import sentencepiece
>>> torch.nn.Module()
Segmentation fault
$ python
>>> import sentencepiece
>>> import torch
>>> torch.nn.Module()
Module()
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#505 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APYK5723XFXXE4CE572NFYDRXHH5NANCNFSM4NY4KIIQ>
.
|
I am confused, it is fresh install of ubuntu 20.04 and Cuda 11. I hope the
sources do not bundle the toolchain.
…On Sat, Jun 20, 2020 at 3:10 AM Guillaume Klein ***@***.***> wrote:
I think it's the same problem actually. The issue can occur when you don't
use the same compiler toolchain to build different Python module.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#505 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APYK577AXGU5HLY3FUPKZULRXROGTANCNFSM4NY4KIIQ>
.
|
Seems we can't reproduce this bug after torch>=1.5.0. Let me close this bug. If you reproduce the errors, please let me know. |
Not sure how related this is but it might help. Here's my stack trace |
Not reproduced on sentencepiece v0.1.95 |
with newly released
sentencepiece==0.1.92
However, downgrade to
sentencepiece==0.1.91
solves this issueThe text was updated successfully, but these errors were encountered: