-
Notifications
You must be signed in to change notification settings - Fork 615
BeamSearchDecoder segmentation fault (on GPU) #1109
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
Comments
Does it also segfault when using the tagged releases Addons 0.8.2 and TensorFlow 2.1.0? |
@guillaumekln This example works (almost) with:
However the snippet above returns a TypeError
and can be made to work by having a positional My internal project (soon to be publicly released) doesn't seem to work on tf 2.1, triggering the following error in training:
which appears to be fixed in the nightlies (probably tensorflow/tensorflow@7f347e6) since the segfault occurs in evaluation, so unfortunately I cannot fall back to the tagged releases anyway. |
Let's close this issue as TensorFlow Addons is built against TensorFlow stable. In consequence, TensorFlow nightlies are not supported. #1281 added explicit runtime checks on the required TensorFlow version. |
@guillaumekln |
The issue only affects the non stable versions of TensorFlow. Can you try with TensorFlow 2.1 instead? |
As @georgesterpu mentioned earlier BeamSearchDecoder with @tf.function doesn't work with TF2.2 nightly neither with TF 2.1. In second case:
I have encountered exactly the same problem as @georgesterpu have. Now the only way to run BeamSearchDecoder as I see is to move to the TF 1, but I don't think that it is a good solution. |
Ok, I thought you were referring to the Segmentation fault issue. Do you mind opening a separate issue for the Insufficient elements error along with a code snippet to reproduce it? |
System information
Describe the bug
Calling a BeamSearchDecoder results in a Segmentation fault (core dumped).
Code to reproduce the issue
Other info / logs
Code on colab
Not sure if this is related to #990, as the issue targets tensorflow-cpu.
In eager mode the code still crashes with the following output:
The text was updated successfully, but these errors were encountered: