Exceptions on nearly every keystroke in 3214

Yup, I was able to reproduce this. Only happens when typing with structure
view open. So I'm affraid you either need to revert to previous build or
do not use structure view.

-

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

I don't suppose there's a workaround for this? It's going to force me
to retreat yet again. It seems like there hasn't been a usable EAP
build since 3144.

This exception seems to happen every few seconds while I'm actively
typing into a source file. (I reported it via the built-in exception
reporting system.)

Error message: Assertion failed
java.lang.Throwable
at com.intellij.openapi.diagnostic.Logger.assertTrue(Logger.java:64)

at com.intellij.openapi.diagnostic.Logger.assertTrue(Logger.java:72)

at com.intellij.psi.impl.a.d.<init>(d.java:14)

at com.intellij.psi.impl.a.a.createSmartPsiElementPointer(a.java:54)

at com.intellij.ide.structureView.a.c.a.<init>(a.java:16)

at com.intellij.ide.structureView.a.a.b.<init>(b.java:9)

at com.intellij.ide.structureView.a.a.c.<init>(c.java:5)

at com.intellij.ide.structureView.a.a.f.d(f.java:4)

at com.intellij.ide.structureView.a.c.a.getChildren(a.java:4)

at com.intellij.ide.util.treeView.a.c.e(c.java:16)

at com.intellij.ide.util.treeView.a.a.b(a.java:46)

at com.intellij.ide.util.treeView.a.a.a(a.java:32)

at com.intellij.ide.util.treeView.a.a.getChildren(a.java:47)

at com.intellij.ide.util.treeView.a.d.getChildElements(d.java:8)

at
com.intellij.ide.util.treeView.AbstractTreeBuilder.b(AbstractTreeBuild
er.java:277)

at
com.intellij.ide.util.treeView.AbstractTreeBuilder.updateSubtree(Abstr
actTreeBuilder.java:311)

at com.intellij.ide.util.treeView.n.b(n.java)

at com.intellij.ide.structureView.b.d$0.b(d$0.java:1)

at com.intellij.ide.util.treeView.n.a(n.java:6)

at com.intellij.ide.util.treeView.n$0.run(n$0.java:10)

at com.intellij.util.Alarm$1.run(Alarm.java:85)

at com.intellij.util.Alarm$2.run(Alarm.java:227)

at com.intellij.openapi.application.impl.c$b_.run(c$b_.java:5)

at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)

at
com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java
:165)

at com.intellij.ide.IdeEventQueue.a(IdeEventQueue.java:143)

at
com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:118)

at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThr
ead.java:201)

at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThrea
d.java:151)

at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)

at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)

at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

Sounds like a good warning - I downloaded it, but rather than unpacking it, I think I'll revert to 3144

Interesting, I reported this from within IDEA (B#3212, also happens there) but although successfully sent I couldn't find it now in the tracker.
This only seems to happen when typing a method/variable name, I can type e.g. "public void" without problems, only when I go on with "myMethod", the exception occurs. It also doesn't occur when typing "slowly" (leaving about 1 sec. between characters)... strange, isn't it?

regards,

Messi

P.S.: Structure view open, of course

max@jetbrains.com wrote:

Yup, I was able to reproduce this. Only happens when typing with
structure view open. So I'm affraid you either need to revert to
previous build or do not use structure view.

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

>

I've wondered whether you guys actually use the EAP builds you release
before you release them. I guess not.

Bernhard Messerer wrote:

Interesting, I reported this from within IDEA (B#3212, also happens
there) but although successfully sent I couldn't find it now in the
tracker.

I'm guessing you mean this request:
http://www.intellij.net/forums/thread.jsp?forum=45&thread=126666#3451651
It was marked fixed for #3214, but the stack trace looks almost exactly like the one in this thread.

Bas

I've wondered whether you guys actually use the EAP
builds you release
before you release them. I guess not.

No, they don't use the EAP builds before releasing them, they use it while releasing them -- after all IDEA is developed using IDEA itself.

If you're expecting them to test every feature before releasing an EAP build, however, you're on the wrong place. Why spend lots of man-hours testing the build when you have a pack of rabid testers (we EAP users) to do this? If you expect bug-free, stable builds, go for the release version. EAP is not for the faint of heart.

thanks for the info, Maxim.
I switched towards using IDEA5 since yesterday.
And as long as I close structure view while editing,
it really is GREAT !!!

Keep up the good work!! ;)

M.

Hello Michael,

I wouldn't go that far. After all, they're only a handfull of people and
with so many combinations I doubt they'd ever manage to test all of them.

And regarding this particular problem, of all the IDEA users I know, no one
edits with the structure view open (on a regular basis, that is). Now we
found out that the jetbrainers don't do it either. :)

Andrei

I've wondered whether you guys actually use the EAP builds you release
before you release them. I guess not.

Marcus Brito wrote:
>>I've wondered whether you guys actually use the EAP
>>builds you release
>>before you release them. I guess not.

No, they don't use the EAP builds before releasing them, they use it while releasing them -- after all IDEA is developed using IDEA itself.

If you're expecting them to test every feature before releasing an EAP build, however, you're on the wrong place. Why spend lots of man-hours testing the build when you have a pack of rabid testers (we EAP users) to do this? If you expect bug-free, stable builds, go for the release version. EAP is not for the faint of heart.

Of course I don't expect them to test every feature. I've been an EAP
participant for years, and I know the drill. On the other hand, I
discovered this particular problem within seconds of launching 3214. And
I do have to wonder about the wisdom of releasing a build that is so
fundamentally broken than a lot of people won't use it. I mean, the
whole point of the EAP is to get people to use the software.

On the other other hand, I'm getting used to working without the
structure pane. So perhaps all is unfolding according to plan after all.