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

terminate called after throwing an instance of 'std::bad_alloc' #1

Open
lidongxing opened this issue Nov 26, 2019 · 1 comment
Open

Comments

@lidongxing
Copy link

when training in the epoch 0:
Epoch: 0 Update: 2000 Loss/word: 0.1851001669525793 Words/sec: 491.82868998145267 Sents/sec: 17.436299743509096

the error occurs:
terminate called after throwing an instance of 'std::bad_alloc'

@rsennrich
Copy link
Contributor

This is unlikely to be a bug, and typically points to your memory being full. Can you try again and keep an eye on memory consumption?

Once confirmed, you can consider whether there's other processes competing for resources that you can stop, whether you can reduce memory consumption of this process (e.g. by reducing batch size), or whether you should consider using a machine with more RAM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants