please, http://www.jetbrains.net/jira/browse/IDEADEV-38536 关注
For whatever reason or unfortunate code inspection configuration causes it, maia just gets caught in an infinite loop of:
-) attempting to run inspections on a file
-) running in to this error and reporting
-) > continue inspections and start over
I'd really really love to use maia now but I can't seem to get away with even a couple minor edits before it crops up. Class cast errors can't be too hard to kill off? (sure you're busy so no big deal, just un-fun) Doesn't happen in Diana of course, but that car isn't as shiny.
it would be easy to fix but this cast just can not exist ;)
Could you please describe your environment? Which OS, jdk version, installed
plugins do you use? We suspect that the issue is caused by inaccurate instrumentation
or smth similar but we can't reproduce it.
Thank you for your feedback
"Develop with pleasure!"
Thank you for taking the time to re-produce this. I had a bad feeling I was the only one experiencing it. Luckily though, I think it might not be entirely impossible to re-produce once I give you some more information as it's fairly consistent for me no matter which project or source file I start editing code in.
-) Happens up to the current #10624 Maia release.
-) OS: OS X 10.5.8 interl core 2 duo
-) Java version: java version "1.6.0_15"
Java(TM) SE Runtime Environment (build 1.6.0_15-b02-215)
Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-87, mixed mode)
I always make a few modifications once I've installed a fresh release as well:
-) Replace default "idea" 32 bit application stub under the Contents/MacOS/ directory with a 64 bit application stub.
-) Edit the info.plist properties with:
2) apple.awt.graphics.UseQuartz:false (As per the recent jdk release notes from apple, they indicate that the newer sun2d renderers are actually faster than quartz in 1.6)
3) VMOptions: -Xms64m -Xmx824m -XX:MaxPermSize=164m -XX:PermSize=24M -XX:TargetSurvivorRatio=1 -XX:SurvivorRatio=2 -XX:+CMSClassUnloadingEnabled -Djava.net.preferIPv4Stack=true -XX:+DoEscapeAnalysis -Xverify:none -XX:+UseAdaptiveSizePolicy -XX:BiasedLockingStartupDelay=0 -Xbootclasspath/a:../lib/boot.jar -ea -agentlib:yjpagent=disablej2ee
-) The installed plugins I'm using:
-) I ran an experiment yesterday where I moved the existing Intellij90 ~/Library/Caches/Intellij90 to a different name to be sure it wasn't picking up any old / bad configurations and then launched maia again. I did log in to the idea server when starting up using my jkuhnert username (feel free to use account if it helps test, can email password if you can't get use it without...it's a throwaway password anyways) in order to download my "shared configuration" settings and bug still cropped up regardless.
-) Usually only takes editing a line of java code or similar to have it happen. (I usually just take an existing somObject.doSomething() call and force the doSomething part to a new line or similar, just enough to get the inspections to run again)
Let me know if I can do anything else to make debugging easier, I'll probably be abnormally earnest in being helpful as I would very much like to be able to use the new version. =)
Please find my comments in jira: http://www.jetbrains.net/jira/browse/IDEADEV-38536
"Develop with pleasure!"
Of course now I've been editing code in maia for about an hour without this happening at all, so it seems my computer is out to subvert me however it can. I'm sure it ~will~ start happening again but at that point I'll probably have no idea at all what the cause of it will be.
Maybe a certain # of IDE restarts will start it happening again? I do remember a brief period when trying the new version where it didn't happen at all and I started happily coding thinking it was all fixed until it resumed the previous behavior. Could it be some sort of compilation / disk cache of classes or data over time? Bah. All I know for sure is that once the exceptions start getting thrown restarting the IDE again has them come back within minutes of code editing and seems to mostly stay that way ...until "some unknown event, perhaps OS restart and clearing out of tmp data" makes it all go away again.