PSI exceptions every second or third keystroke.....

Who else is getting endless PSI related exceptions every time they hit a
keystroke or so?

So times its making me restart IDEA after about a minute or less of usage,
sometimes I can go hours.... arrrrg.

I'm also noticing some weird swing/thread related issues, where I'll start
typing, and IDEA does nothing, but if I alt-tab out, then tab back in -
the keystrokes get played out ( even thou the cursor might not actually do
where I'd left it... erk :(

9 comments
Comment actions Permalink

same here

Mark Derricutt wrote:

>Who else is getting endless PSI related exceptions every time they hit a
>keystroke or so?
>
>So times its making me restart IDEA after about a minute or less of usage,
>sometimes I can go hours.... arrrrg.
>
>I'm also noticing some weird swing/thread related issues, where I'll start
>typing, and IDEA does nothing, but if I alt-tab out, then tab back in -
>the keystrokes get played out ( even thou the cursor might not actually do
>where I'd left it... erk :(
>

>

0
Comment actions Permalink

If you are running on Linux and JDK 1.5, update to 1.5_03 and the problem with the editor eating the keystokes seems to go away.

0
Comment actions Permalink

On Mon, 02 May 2005 19:17:40 +0400, Michael Garza wrote:

If you are running on Linux and JDK 1.5, update to 1.5_03 and the problem
with the editor eating the keystokes seems to go away.


Yep - no longer eating keystrokes, but the legion of PSI exceptions is
different...

0
Comment actions Permalink

Mark,
I've just looked at those exception you've submitted. It seems repository
caches are corrupted for your project. As they're corrupted no fix to the
corruption will recover them so I'd recommed to clean them up. Delete contents
of the system/caches folder and exception will stop happening.

-


Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

On Mon, 02 May 2005 19:17:40 +0400, Michael Garza wrote:

>> If you are running on Linux and JDK 1.5, update to 1.5_03 and the
>> problem with the editor eating the keystokes seems to go away.
>>

Yep - no longer eating keystrokes, but the legion of PSI exceptions is
different...



0
Comment actions Permalink

On Tue, 03 May 2005 08:39:40 +0000, Maxim Shafirov wrote:

Mark,
I've just looked at those exception you've submitted. It seems repository
caches are corrupted for your project. As they're corrupted no fix to the
corruption will recover them so I'd recommed to clean them up. Delete
contents of the system/caches folder and exception will stop happening.


I seem to be doing an rm -rf every day thou. So my only guess is that
something is corrupting the caches often. Just rm'd them again and will
keep an eye out for exceptions...

0
Comment actions Permalink

On Tue, 03 May 2005 21:06:45 +1200, Mark Derricutt wrote:

I seem to be doing an rm -rf every day thou. So my only guess is that
something is corrupting the caches often. Just rm'd them again and will
keep an eye out for exceptions...


Actually - how about have IDEA "know" to do this for me?

If it detects that the caches are corrupt, tell me - ask me if I want to
clear the caches and rebuild from scratch. If IDEA did this itself -
would we need to exit/restart IDEA at all? ( automatically deleting the
caches and quiting would be acceptable, similar to what happens after
installing/updating plugins )

0
Comment actions Permalink

Good idea, except that's functionality that's probably only going to
have value during the EAP cycle. Or is it?
R

0
Comment actions Permalink

Robert Gibson wrote:

Good idea, except that's functionality that's probably only going to
have value during the EAP cycle. Or is it?


That's no reason for them not to include it in the EAP and then disable
it in normal releases.

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://www.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: (416) 933-5046 | Fax: (416) 933-5001

0
Comment actions Permalink

On Tue, 03 May 2005 11:23:25 -0400, Gordon Tyler wrote:

That's no reason for them not to include it in the EAP and then disable it
in normal releases.


I don't see any reason to NOT leave it in the final product either. Now
that the exception handler/display is not as obtrusive as it once was, if
you're still getting exceptions, and corrupted indexes in the released
version, you still want to know about it, and deal with it.

0

Please sign in to leave a comment.