comments/complaints about product: 3.0 + through to 915
Hi I would like to make a few observations, that perhaps you can comment on.
I was running 657 (prio to 3.* release) and life was good, except it had one problem it occasionally ran out of memory and hung. That problem prompted me to go for an upgrade.... I went to 3.0.5 and found that this version had a sever memory leak, I could only run my project for about 10 minutes before having to reboot. I update mx to 250mb but it rapidly reached that point. Now I am on the EAP's (915) and finding that there are a lot of little things that are frustratingly different.
1) the caching of files seems to get more confused - I have two projects open and one will update (create new files) the other. I close out the #2 project, run #1 and then open #2 (all with the same IntelliJ session) and #2 files are the same as I left them in the editor (the disk version is new, but the cached editor doc is out of date). It is not checked upon rebuild, and I get errors ..etc.
2) memory usage (memory leak) still seems to be around although not as bad as 3.0.5.
3) From my prior posting "Instant feedback on syntax for #915" - the syntax checker is slow and doesn't work very accurately. This is by far the biggest problem for me. Since I relied on the syntax checker for increased productivity.
Any comments? When will the next version be out? By posting this message am I getting to the developers of IntelliJ???
By the way, I love the product, I just don't want to see it slipping away into bug-dome. (I guess there has always been one grievance - I don't like the auto file synchronization - it is a pain-in-the butt!! - I want to save my files when and where I'd like to save them, also I'd like to be able to do a "save as")... Thanks for listening.
Thanks,
Joel
Please sign in to leave a comment.
Uh oh.
:)
(Dan, where are you? Shall I tell Joel to stop whining?)
Just kidding Joel. Dan was giving me a hard time last week.
I can't speak to the first three points, but yes, these comments make it to
the Jetbrains developers. And as for file synchronization...I struggled
with that for a while when I first started using IDEA. I've since learned
to adjust to work under their metaphor and I haven't had any problems.
I can't think off too many things I am having problems with. No
showstoppers, anyway. Taglib resolution could be better implemented. A
help file would be very useful (I don't keep 3.0 around--I just use the
license that came with it). It's a whole lot faster, especially recently.
My small beef would be with "Performing optimization..." on startup. With
all the JARs/source/content I have on my project, it takes forever. Let's
be blunt and brutally honest: the message should say "go get a cup of
coffee; it'll be a while".
But once I am in and coding, it's pretty solid. Personally, I wouldn't go
back to 3.0. 915, and nearly all of the builds, are good enough for
everyday real work.
"Joel" <no_mail@jetbrains.com> wrote in message
news:19652249.1063059183160.JavaMail.itn@is.intellij.net...
on.
>
one problem it occasionally ran out of memory and hung. That problem
prompted me to go for an upgrade.... I went to 3.0.5 and found that this
version had a sever memory leak, I could only run my project for about 10
minutes before having to reboot. I update mx to 250mb but it rapidly reached
that point. Now I am on the EAP's (915) and finding that there are a lot of
little things that are frustratingly different.
>
open and one will update (create new files) the other. I close out the #2
project, run #1 and then open #2 (all with the same IntelliJ session) and #2
files are the same as I left them in the editor (the disk version is new,
but the cached editor doc is out of date). It is not checked upon rebuild,
and I get errors ..etc.
>
as 3.0.5.
>
syntax checker is slow and doesn't work very accurately. This is by far the
biggest problem for me. Since I relied on the syntax checker for increased
productivity.
>
am I getting to the developers of IntelliJ???
>
into bug-dome. (I guess there has always been one grievance - I don't like
the auto file synchronization - it is a pain-in-the butt!! - I want to save
my files when and where I'd like to save them, also I'd like to be able to
do a "save as")... Thanks for listening.
>
Joel, please see below
--
regards,
Alexey Kudravtsev.
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"
close out the #2 project, run #1 and then open #2 (all with the same IntelliJ session) and #2 files are the same as I left them in
the editor (the disk version is new, but the cached editor doc is out of date). It is not checked upon rebuild, and I get errors
..etc.
This definitely looks like a bug, so if you can post the sample project where this isuue can be reproduced to the
www.intellij.net/tracker , we will fix that asap
>
>
is by far the biggest problem for me. Since I relied on the syntax checker for increased productivity.
Again, we will be grateful if you post concrete test cases for the syntax checker "inaccuracy" to the tracker.
>
Yes you are!
>
grievance - I don't like the auto file synchronization - it is a pain-in-the butt!! - I want to save my files when and where I'd
like to save them, also I'd like to be able to do a "save as")... Thanks for listening.
>
This sounds like a defect
General profiling is done at the end of the release. If you can isolate it down to a specific, then by all means report it (in the tracker).
PErformance problems are typically not fixed until the end of the release unless there is a very severe, or specific problem that they can address. Try turning off various error checking (options->editor->errors), and seeing if you can figure out exactly which check is causing the performance issue. The file it in a tracker.
Maybe. The best way to get their attention is to file a defect in the tracker.
Mike