PyCharm 2017.1 is a nightmare
Failure:
...edit in pycharm
...leave pycharm windows to do something else
...go back and click pycharm windows
(boom!)
...PyCharm will do the INDEX, AND EVERY, EVERY FILE you've opened and in edit will BE CLOSED, the unfolded file tree in project explorer will be folded to a simple, tidy, clean project folder. AND I HAVE to RE-CLICK in the project explorer to go to the indeed file I want to work with, RE-OPEN every file I want to code
...leave pycharm again to do more things
...then go back and click pycharm windows again
(boom!)
...AGAIN, PyCharm do the Fxxx INDEX, CLOSE ALL FILES and UNFOLD PROJECT EXPLORER TREE
Environment:
Windows 7 Enterprise on Thinkpad T420.
PyCharm 2017.1
Build #PY-171.3780.115, built on March 24, 2017
Licensed to EMC
JRE: 1.8.0_112-release-736-b13 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 7 6.1
I love PyCharm, but I hate PyCharm 2017.1
Please sign in to leave a comment.
same problem here, (temporary solution) create an additional project in a new window, then the behaviour of the second window is better?
Hi, Nigelibrown, a new project in second window will not crash.
But with further investigation, I believe "second window" is not a solution, while it might fail due to project size, large project with more file is easier to crash.
After upggrading to 2017.1, PyCharm doesn't find my Vagrant environment any more. Hope there's a way to downgrade PyCharm.
Hello, thank you for the reports!
Please contact pycharm-support@jetbrains.com with your idea.log (https://intellij-support.jetbrains.com/hc/en-us/articles/207241085-Locating-IDE-log-files). Thank you.
Thanks Anna for offering a report channel, I've reported my log to support team and look forward to a solid fix.
Update:
I work on Windows 7, remote server provide SAMBA access. The project on SAMBA opened in local PyCharm will 100% fail.
While the project of local files will not have this problem.