PHP Storm 2.1 on OSX a step backwards in stability and reliability?
I recently upgraded to PHP Storm 2.1 [Build #PS-107.120] on OS-X and ever since I've noticed a variety of issues:
- Memory use: The bar in the corner seems to sit at around 500 / 795M. In 2.0.1 this would be more like 200 / 495M. The extra memory is a problem when running lots of apps side by side (I have 4GB memory on my laptop and this is starting to feel like it's not enough).
- Clipboard access: Sometimes PHP Storm refuses to notice that I've copied something into the clipboard from outside the program and instead pastes the same thing that I last copied in PHP Storm. In the previous version of PHP Storm clipboard access worked flawlessly (including Cmd+Shift+V giving me a history of items from the clipboard and allowing me to choose which one to paste.
- Random crashes: PHP Storm 2.1 has crashed multiple times (the previous version never did). Mostly after the laptop has woken from sleep and then I start trying to use PHP Storm. Looking in the log file I think that the most recent crash may be associated with "stubs.SerializationManagerImpl - PersistentStringEnumerator storage corrupted" or possibly this:
2011-06-05 10:04:04,695 [ 134077] ERROR - currency.PrioritizedFutureTask - java.lang.NoSuchFieldError: l
java.util.concurrent.ExecutionException: java.lang.NoSuchFieldError: l
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at com.intellij.concurrency.PrioritizedFutureTask.access$301(PrioritizedFutureTask.java:31)
at com.intellij.concurrency.PrioritizedFutureTask$1.run(PrioritizedFutureTask.java:77)
at com.intellij.concurrency.PrioritizedFutureTask.run(PrioritizedFutureTask.java:113)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.lang.NoSuchFieldError: l
at net.sf.cglib.proxy.AdvancedEnhancer.create(AdvancedEnhancer.java:313)
at net.sf.cglib.proxy.AdvancedProxy.createProxy(AdvancedProxy.java:112)
at net.sf.cglib.proxy.AdvancedProxy.createProxy(AdvancedProxy.java:90)
at net.sf.cglib.proxy.AdvancedProxy.createProxy(AdvancedProxy.java:76)
at com.intellij.util.xml.impl.DomInvocationHandler.<init>(DomInvocationHandler.java:125)
at com.intellij.util.xml.impl.DomRootInvocationHandler.<init>(DomRootInvocationHandler.java:32)
at com.intellij.util.xml.impl.DomFileElementImpl.<init>(DomFileElementImpl.java:126)
at com.intellij.util.xml.impl.FileDescriptionCachedValueProvider.a(FileDescriptionCachedValueProvider.java:118)
at com.intellij.util.xml.impl.FileDescriptionCachedValueProvider.getFileElement(FileDescriptionCachedValueProvider.java:71)
at com.intellij.util.xml.impl.DomManagerImpl.getFileElement(DomManagerImpl.java:344)
at com.intellij.util.xml.impl.DomManagerImpl.getFileElement(DomManagerImpl.java:56)
at com.intellij.util.xml.DomManager.getDomFileDescription(DomManager.java:171)
at com.intellij.util.xml.DomFileIconProvider.getIcon(DomFileIconProvider.java:33)
at com.intellij.util.PsiIconUtil.getProvidersIcon(PsiIconUtil.java:43)
at com.intellij.psi.impl.ElementBase.computeIconNow(ElementBase.java:115)
at com.intellij.psi.impl.ElementBase.access$000(ElementBase.java:48)
at com.intellij.psi.impl.ElementBase$1.fun(ElementBase.java:57)
at com.intellij.psi.impl.ElementBase$1.fun(ElementBase.java:52)
at com.intellij.ui.DeferredIconImpl$2.run(DeferredIconImpl.java:181)
at com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:767)
at com.intellij.ui.IconDeferrerImpl.evaluateDeferredInReadAction(IconDeferrerImpl.java:99)
at com.intellij.ui.DeferredIconImpl.evaluate(DeferredIconImpl.java:192)
at com.intellij.ui.DeferredIconImpl$1.run(DeferredIconImpl.java:115)
at com.intellij.concurrency.JobUtil$3.call(JobUtil.java:133)
at com.intellij.concurrency.JobUtil$3.call(JobUtil.java:130)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at com.intellij.concurrency.PrioritizedFutureTask.access$101(PrioritizedFutureTask.java:31)
at com.intellij.concurrency.PrioritizedFutureTask$1.run(PrioritizedFutureTask.java:70)
... 4 more
2011-06-05 10:04:04,775 [ 134157] ERROR - currency.PrioritizedFutureTask - JetBrains PhpStorm 2.1 Build #PS-107.120
2011-06-05 10:04:04,775 [ 134157] ERROR - currency.PrioritizedFutureTask - JDK: 1.6.0_24
2011-06-05 10:04:04,776 [ 134158] ERROR - currency.PrioritizedFutureTask - VM: Java HotSpot(TM) 64-Bit Server VM
2011-06-05 10:04:04,776 [ 134158] ERROR - currency.PrioritizedFutureTask - Vendor: Apple Inc.
2011-06-05 10:04:04,776 [ 134158] ERROR - currency.PrioritizedFutureTask - OS: Mac OS X
2011-06-05 10:04:04,776 [ 134158] ERROR - currency.PrioritizedFutureTask - Last Action:
2011-06-05 10:04:04,776 [ 134158] ERROR - currency.PrioritizedFutureTask - Original exception:
java.lang.NoSuchFieldError: l
at net.sf.cglib.proxy.AdvancedEnhancer.create(AdvancedEnhancer.java:313)
at net.sf.cglib.proxy.AdvancedProxy.createProxy(AdvancedProxy.java:112)
at net.sf.cglib.proxy.AdvancedProxy.createProxy(AdvancedProxy.java:90)
at net.sf.cglib.proxy.AdvancedProxy.createProxy(AdvancedProxy.java:76)
at com.intellij.util.xml.impl.DomInvocationHandler.<init>(DomInvocationHandler.java:125)
at com.intellij.util.xml.impl.DomRootInvocationHandler.<init>(DomRootInvocationHandler.java:32)
at com.intellij.util.xml.impl.DomFileElementImpl.<init>(DomFileElementImpl.java:126)
at com.intellij.util.xml.impl.FileDescriptionCachedValueProvider.a(FileDescriptionCachedValueProvider.java:118)
at com.intellij.util.xml.impl.FileDescriptionCachedValueProvider.getFileElement(FileDescriptionCachedValueProvider.java:71)
at com.intellij.util.xml.impl.DomManagerImpl.getFileElement(DomManagerImpl.java:344)
at com.intellij.util.xml.impl.DomManagerImpl.getFileElement(DomManagerImpl.java:56)
at com.intellij.util.xml.DomManager.getDomFileDescription(DomManager.java:171)
at com.intellij.util.xml.DomFileIconProvider.getIcon(DomFileIconProvider.java:33)
at com.intellij.util.PsiIconUtil.getProvidersIcon(PsiIconUtil.java:43)
at com.intellij.psi.impl.ElementBase.computeIconNow(ElementBase.java:115)
at com.intellij.psi.impl.ElementBase.access$000(ElementBase.java:48)
at com.intellij.psi.impl.ElementBase$1.fun(ElementBase.java:57)
at com.intellij.psi.impl.ElementBase$1.fun(ElementBase.java:52)
at com.intellij.ui.DeferredIconImpl$2.run(DeferredIconImpl.java:181)
at com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:767)
at com.intellij.ui.IconDeferrerImpl.evaluateDeferredInReadAction(IconDeferrerImpl.java:99)
at com.intellij.ui.DeferredIconImpl.evaluate(DeferredIconImpl.java:192)
at com.intellij.ui.DeferredIconImpl$1.run(DeferredIconImpl.java:115)
at com.intellij.concurrency.JobUtil$3.call(JobUtil.java:133)
at com.intellij.concurrency.JobUtil$3.call(JobUtil.java:130)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at com.intellij.concurrency.PrioritizedFutureTask.access$101(PrioritizedFutureTask.java:31)
at com.intellij.concurrency.PrioritizedFutureTask$1.run(PrioritizedFutureTask.java:70)
at com.intellij.concurrency.PrioritizedFutureTask.run(PrioritizedFutureTask.java:113)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Has anyone else seen problems like this? Are they known issues? Is there any workarounds (other than using 2.0.1 instead!)?
The projects I am editing are all stored in git and are a combination of PHP/ HTML/ JS and CSS code.
Please sign in to leave a comment.
Hello,
i can confirm Clipboard and Crashes (2.1 and latest EAP). Not very often - so i thought it was "my fault" with the clipboard.
I have discovered some crashes when opening a project on a samba-volume.
Another thing in the 2.1 and latest EAP: the local history for files takes very lon to load. If you want to show the local history on a project tree, it takes forever... You can still close the history window.
Memory access: Right now PHPstorm is using 71M out of 795M of memory in the heap. BUT I'm running 64bit an have a recent MBP with 8GB of RAM.
Clipboard access: I have this problem too. And a related issue, I use TextExpander.. which does not work with PHPStorm. I think PHPStorm's handling of the clipboad is the issue.
Random crashes: I can also confirm this. Though rarely. Though I don't keep PHPStorm running. I will now and report what happens to be when waking from "sleep".
Ok. The IDE sometime crashes after waking up. A few times I had to kill the app to even restart it. I can't pin point why though. Since I can't repordice it at will.
Also other unusual issues are cropping up. Like I was trying to type "<li>". But code hinting would pop up and only display "Link" and insert "link href="" rel="">". Happened a few times. And yes I was under a <ul> tag. After a restart it was fine.
Another example: editing a CSS file the IDE would not let me type a lower case l. Everytime I typed "l" it would appear as "L". I had to shut down PHPStorm and do the edit in BBedit. And again, after a restart it was fine.
PS: Have you guys tried the EAP version yet?
So it seems like lots of people are running into these issues... Can anyone from Jet Brains chime in and confirm the problems? Or does this need to be reported somewhere else? In the meantime I'll have to continue using 2.0.1 which seems much more stable!
@Stephen - no, I haven't tried the EAP...
Well - what can I say here...
Judging from overall feedback only very small amount of users report these problems. Many JB devs use Mac's daily for all development tasks so we usualy are aware of any significant problems or degradations. And now we are not too alarmed and definitely can't accept what sait in the title.
The clipboard and some particular stability and performance problems are reported and some of reported are alread fixed in EAP.
Anyway its useless to start such general duscussions. We tackle with problems once we are able to reproduce them and find a solution. Just submit *proper* bug reports, and especially proper performance reports into tracker and we'll investigate.
Wow. Is that seriously an official response? So sorry for using your software!
The fact that multiple people jumped on this thread and reported identical problems seems to suggest that these are real problems that are affecting a number of your paying customers.
I'm happy to submit specific bug reports - this thread was to judge if other people were having problems and to try to establish what specific bits of my setup might be contributing to the problems. If you look through the thread you'll see I've tried to provide helpful information to narrow down what it might be that is causing the problems. I'd assume that you couldn't possibly ship something with problems this serious for ALL users so it might be related to specifics of my projects or my computer. Like I've said, PHP Storm 2.0.1 worked fine on my projects and 2.1 is a step backwards for me.
Please tell me what information I can provide and so that I can help you fix these bugs.
p.s. I would install the EAP but I would generally assume that unreleased beta software is less stable than official releases. Since I use the software professionally I try to stick to released versions to minimise the chance of things effecting my code or my productivity.
Actually I've had less issues with the EAP version. But some clipboard issues still exists. But it hasn't crashed once.
Generally the EAP versions are stable. Stable enough to do work in. Download it and give it a try.
Well, I'm terribly sorry to disappoint you.
I was just trying to give you practical and constructive answer.
Plus give you bit of our perspective - we monitor feedback on our releases and EAP builds daily. And we can't see anything that can be generalised even closely to your post.
And of course you may peruse our resources to contact other PhpStorm users and gather any type feedback they willing to provide to you.
But we don't need such general thread. Except for very dumb bugs that occur in EAP and are fixed in matter of hours or general and well known restrictions the roots of performance problems are diffrerent in every case. So only thing we need and will react to is always a separate *proper* bug reports in tracker.
Thanks Stephen. I installed the EAP release last Friday and have definitely found it to be more stable. I'm still having issues with the clipboard (although it seems less common) but the memory usage is significantly down and I haven't had so many crashes... I'd just expect a proper release to have had more QA and testing - it feels like 2.1 was rushed out the door a little (so that people who bought a license on day 1 would be eligable for an upgrade?)
Thanks for the further response. Your initial reply didn't seem at all practical and constructive, it seemed much more defensive than anything else.
I might have muddied things a little by lumping a number of different faults together but 2.1 felt so unfinished to me that I assumed they were related.It seems from your response that you still think my main issue was with performance but that is only one of the three issues I mention.
The aim of the thread was to find out if what I was seeing was bugs and what extra information might be relevant to help reproduce them. If you read back through my contributions to the thread you will see that I have asked a number of times where I should submit these as bugs (once I have enough information to provide a detailed bug report). You will also see that I have tried to help narrow down the problem (and that I started by posting what looked like it might be useful information from my log file).
Maybe this time you can point me to the bug tracker and information on what should be included in a *proper* bug report and I will try to submit one if I experience further problems with the EAP which prevent me from being able to work effectively.
As the forums announcement banner says, all bug reports and feature requests should be posted separately directly to the project issue tracker http://www.jetbrains.net/tracker/issues/WI
Links to all our resources are listed both on main and EAP download pages, see http://confluence.jetbrains.net/display/WI/Web+IDE+EAP
Please note that many bugs you experience may be already reported and even fixed in unpublished builds, so you may excersise seach before putting your effort into the description.
As for performance reports please consult http://devnet.jetbrains.net/docs/DOC-192