Skip to content
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

tf.keras.backend.arange crash (abort) when start is large #46889

Closed
DNXie opened this issue Feb 3, 2021 · 4 comments · Fixed by #51711
Closed

tf.keras.backend.arange crash (abort) when start is large #46889

DNXie opened this issue Feb 3, 2021 · 4 comments · Fixed by #51711
Assignees
Labels
comp:keras Keras related issues stat:awaiting tensorflower Status - Awaiting response from tensorflower TF 2.1 for tracking issues in 2.1 release type:bug Bug

Comments

@DNXie
Copy link

DNXie commented Feb 3, 2021

System information

  • Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
  • Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
  • TensorFlow installed from (source or binary): binary
  • TensorFlow version (use command below):2.1.0
  • Python version:3.7.6
  • Bazel version (if compiling from source):N/A
  • GCC/Compiler version (if compiling from source):N/A
  • CUDA/cuDNN version:N/A
  • GPU model and memory:N/A

Describe the current behavior
tf.keras.backend.arange crash (abort) when start is large
Describe the expected behavior
expect no crash

Standalone code to reproduce the issue

import tensorflow as tf
tf.keras.backend.arange(start=1e+38)

Output:

2021-02-03 16:53:49.181545: F tensorflow/core/framework/tensor_shape.cc:187] Non-OK-status: InitDims(dim_sizes) status: Internal: Expected shape dimensions to be non-negative, got -9223372036854775808
Aborted (core dumped)
@DNXie DNXie added the type:bug Bug label Feb 3, 2021
@ravikyram ravikyram added comp:keras Keras related issues TF 2.1 for tracking issues in 2.1 release labels Feb 3, 2021
@ravikyram
Copy link
Contributor

I have tried in colab with TF version 2.4, nightly version(2.5.0-dev20210203) and was able to reproduce the issue. Please, find the gist here. Thanks!

@ravikyram ravikyram assigned ymodak and unassigned ravikyram Feb 3, 2021
@ymodak ymodak added the stat:awaiting tensorflower Status - Awaiting response from tensorflower label Feb 4, 2021
@sushreebarsa
Copy link
Contributor

Was able to reproduce the issue in TF 2.6.0-dev20210528,please find the gist here..Thanks !

@yongtang
Copy link
Member

The issue will be fixed by PR #51711.

@google-ml-butler
Copy link

Are you satisfied with the resolution of your issue?
Yes
No

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp:keras Keras related issues stat:awaiting tensorflower Status - Awaiting response from tensorflower TF 2.1 for tracking issues in 2.1 release type:bug Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants