2.1.5 - Indexing Problem and Lock-Up Follow Keith Davis Created September 19, 2011 19:37 This might be preliminary, so has anyone had trouble with 2.1.5 locking up or taking longer / indexing too much???
Now, just locked up while Inspecting.
Its kind of pointless to discuss the observations in this way.
Please follow http://devnet.jetbrains.net/docs/DOC-192
I was just trying to get some feedback to see if others had noticed a difference since 2.1.4 (we appear to be) before I spend valuable time chasing that down. If it does appear to be a problem, then I will roll my team back to 2.1.4 while until the issue is resolved.
I see your point.
We have not received any other reports with such problems. Albeit not many users probably upgraded, since we haven't announced it much. I'll post an automated update info today.
FYI 2.1.5 does not contain ANY changes in PHP support code, only platform fixes, including some critical improvements to internal caches.
the build numbers are the same to 2.1.4 so think people think the numbering might have been wrong etc..
I updated a few hours ago and have been switching projects a lot (thus re-indexing), but I have not noticed anything out of the ordinary.
I've had a bunch of lockups with 2.1.5 and with the v3 early access.
I just reinstalled 2.1.4 because it's happening way too often.
I'm running on Windows 7 64 bit. I access the web files via a network share[SAMBA to a virtualbox version of linux running on the same machine].
i got the lockups thing now to.. EAP 3.. restarted pc seems to be fine now again.. but yeah.. defs agree.. its not fun.. typing out a bunch of code.. lockup.. bang work gone cause i didnt ctrl + s or loose frame focus.
Win 7 64bit. 16gb ram
We officially do not support working directly over network share and do no accept performance problem reports in such case.
Please use "New project from existing files" wizard to create a local copy and set up auto sync.
mine is on local.. D:\web\
Well, please follow
we are unable to proceed with investigation without any technical info.
Also, @everybody please file your performance problems into issue tracker with required technical info into SEPARATE issues.