-
Notifications
You must be signed in to change notification settings - Fork 50
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
Python2 crashes if tensorboard_logger is imported before torch #25
Comments
wow, that's quite a nasty bug! And thanks for reducing this to a small example.
so the crash happens not on import, right? I tried running the first (problematic) version of the script, and it didn't crash on me (using python 3.6 and same versions of packages). I remember having issues with torch import order like this: pytorch/pytorch#2083 but not the memory corruption. To sum up, I'm not sure I'll be able to help here much, sorry. tensorboard_logger is pure python and is not supposed to do anything nasty, but still I can't explain why this error is happening. This could be some unrelated issue in pytorch or some other C library which is triggered only upon specific conditions, maybe if you obtain the backtrace from the crash this would help to narrow it down. And thank you for the kind words about the library. |
That's correct, the crash happens on the last line, which is the forward pass in the network (I edited the issue for clarity of others.) I guess I just wanted to document this as an issue so that anyone who comes across similar behavior has one idea to try out. And if I figure out that combination of factors that causes the problem, I'll comment here. |
Thanks @kukuruza let's keep it open so that it's more visible in case someone else also has this problem |
Thanks for the great package, it really brings much value for me. But I've recently come across a python crash.
Steps to reproduce. Running the script below causes the crash on the last line (forward pass of the network).
I also found that switching the order of the imports solves the problem. The following works fine.
If I am not using
.cuda()
in the code, any order works fine.System:
Packages:
I installed them with
I assume the order of imports was tested before, so my only guess is that
conda
andpip
don't work well together and load different versions of some package.The text was updated successfully, but these errors were encountered: