We continue talking about our new Node.js profiling features in WebStorm 10. In our previous post we explored CPU profiling. In this one we'll dive into the strategies for memory problems investigation and see how WebStorm can help us apply them. (more…)

Profiling is a hard job. Keeping in mind execution time and code structure is a serious challenge with regard to the huge amount of collected information. WebStorm assists you on this tough journey. It starts a Node.js application with profiling and automatically opens the profile after the run. It points at hot spots by opening and highlighting them in call trees and bringing you immediately to the related source code. The IDE can filter out “noise” by showing only the functions that took too much time. To try this feature right now, start with selecting Record CPU profiling info in

New IntelliJ IDEA 11.1.5 EAP build 117.1006 is available for download. The build contains several important fixes for Subversion VCS support related mostly to SVNKit library: checksum mismatch and BUSY exception problem. The full list of changes can be found in Release Notes. Please feel free to share your feedback and report bugs in our issue tracker. Develop with Pleasure!

In the new EAP we deliver performance and memory usage improvements together with a bunch of Subversion fixes. We especially would mention IDEA-85279 (which introduces better connection pool) and IDEA-75800 (the problem with merge and branch point search had been solved). You can find the complete list of changes in the build. Download it or upgrade from within the IDE using the “Check for updates” feature.

New IntelliJ IDEA 11.1 EAP build (116.32) is available with Subversion 1.7 support finally built in. Here are some details on the current implementation. We don't perform automatic upgrade of your working copies to version 1.7, you can easily do it manually (Changes | Subversion Working Copies | Change). (more…)

The most exciting news for me is that now in forthcoming IntelliJ IDEA 11, we show Git revisions graph! Now that IntelliJ IDEA can visualize commits links, we've added context actions to tag a commit, create (and checkout) new branch, and checkout a selected revision. I want to specifically mention the highlight actions — now you can see what commits are in "ancestors subgraph" for a selected commit. By default, IntelliJ IDEA shows HEAD subgraph, i.e. you see what commits you have in your working tree now. It is really convenient when you are checking what commits went into some tag (or

As for me, after a few years of working in a huge project inside a big team, I became concerned about accidentally breaking the project. That's why every time I commit something, I double-check my changes. In the forthcoming IntelliJ IDEA 11 EAP, I have a special "digest" changes presentation for that! It helps me in my last pre-commit check immediately inside the commit dialog: And I also use it all the time when coding, to recall my changes: NB: to see the digest of changes in Changes | Local, use the new "Change Details" toolbar button. To tell the truth, even when I was in the midd

In IntelliJ IDEA 10.5 we've improved setting up your Perforce server connection and connection state diagnostics. Configuring connections If you are using P4CONFIG files for configuration, IntelliJ IDEA shows what config files it has found and what other default settings are used. This way you can be sure that your P4CONFIG files are found and taken into account. Use the 'Test Connection' button in 'Settings | Version Control | VCSs | Perforce' to see this information. Moreover, in case you specified a wrong client workspace and your project roots do not match with the workspace roots, you a

There's been a number of new things we've added in IntelliJ IDEA 10.5 related to version control support. You can try them already in a latest EAP build. And here's a quick overview. Do not forget things... TODO! Now you can easily ensure you haven't forgotten to implement a method, and double-check the important places in your code before commit. Just mark those places in code with TODO. IntelliJ IDEA's new "Check TODO" before commit inspection will notify about all new and edited TODO items. It will also confirm about TODO items in the changed fragments (in case they are not actual any mor

When diving into code details, the most common question would often be: - Why does this line stay here? When annotation doesn't give the answer, jump into the change contents in one click: (coming in next IntelliJ IDEA EAP)

Feature branches have simple life cycle, they usually consume trunk changes and are merged back into trunk after the work is completed. In IntelliJ IDEA 9.0.3 EAP, take all trunk changes into feature branch and reintegrate back into trunk using new “Merge from…” action: You can merge all changes in one shot or select a subset of them. Changelist with merged changes is created and offered for commit.

In the upcoming Maia EAP you will find a slightly different Commit Changes dialog. Automatic use of JobView filter on search results. Support for Perforce native search query syntax (in an example below we're looking for Job in any field)