Hi,
I encountered a segmentation fault issue with the latest master version of pytorch.
I managed to catch it with gdb and apparently the line where it happened is the following:
torch::autograd::InputBuffer::add (this=this@entry=0x7dc51afefb10, pos=pos@entry=0,                                 |
var=…) at torch/csrc/autograd/input_buffer.cpp:17                                                             |
17        if (!item.first.defined()) {
Any idea of what could cause it? Looks like an issue wit pytorch internals.
Consider that the my code used to perfectly work on a previous commit and the segmentation fault occurs after a random number of epochs/iterations.
Thanks.
Additional backtrace information:
#0  torch::autograd::InputBuffer::add (this=this@entry=0x7dc51afefb10, pos=pos@entry=0,
var=…) at torch/csrc/autograd/input_buffer.cpp:17
#1  0x00007fc6df0cb3ec in torch::autograd::Engine::evaluate_function (
this=this@entry=0x7fc6e03d4040 , task=…)
at torch/csrc/autograd/engine.cpp:268
#2  0x00007fc6df0cc84e in torch::autograd::Engine::thread_main (
this=0x7fc6e03d4040 , graph_task=0x0) at torch/csrc/autograd/engine.cpp:144
#3  0x00007fc6df0c9632 in torch::autograd::Engine::thread_init (
this=this@entry=0x7fc6e03d4040 , device=device@entry=3)
at torch/csrc/autograd/engine.cpp:121
#4  0x00007fc6df0ec11a in torch::autograd::python::PythonEngine::thread_init (
this=0x7fc6e03d4040 , device=3) at torch/csrc/autograd/python_engine.cpp:28
#5  0x00007fc693ebac80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007fc74773f6ba in start_thread (arg=0x7dc51aff0700) at pthread_create.c:333
#7  0x00007fc7474753dd in clone () at …/sysdeps/unix/sysv/linux/x86_64/clone.S:109