22 comments
Comment actions Permalink

Hello Ted,

Is this a known problem? Not sure how to recreate this...exiting IDEA
and reloading the project makes the redness go away.


Yes, this is a known problem, but we haven't found a way to reproduce it
reliably.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


-1
Comment actions Permalink

I've noticed this for a while -- not new to 7718. It comes and goes...

0
Comment actions Permalink

I also have this problem quite often.

Usually it's when there is an error in the java class somewhere that crops
up during a compile. Then I go into the file and fix it and the red mark on
both the java file and the module stay red until I do a rebuild.

this happens all the time for me and my co-worker.



"Anders Wallgren" <anders_wallgren@alum.mit.edu> wrote in message
news:21540338.1204311157492.JavaMail.itn@is.intellij.net...

I've noticed this for a while -- not new to 7718. It comes and goes...


0
Comment actions Permalink

The only thing I've seen like this involves IntelliLang and @RegExp strings. Perfectly valid RE patterns will, at some point during editing, start to show IntelliLang-supplied errors. They stick around until you restart (I can't recall, at the moment, whether closing the file and reopening it clears the spurious error indications). While the source file shows these error indicatinos, there is no problem compiling these files. (Bad RE Pattern strings compile just as well as proper ones, of course.) But these are definitely good RE Patterns that can be used for their intended purpose without objection (or Exception) from the Java RE libraries.

I have not been able to determine any pattern, other than it's fairly common but takes a bit of editing before it shows up. I don't recall every seeing these spurious errors show up, so I think they happen when editing elsewhere in the file, not within the RE Pattern string itself.


Randall Schulz

0
Comment actions Permalink

Hello Dmitry,

Hello Ted,

Is this a known problem? Not sure how to recreate

this...exiting IDEA

and reloading the project makes the redness go

away.

Yes, this is a known problem, but we haven't found a
way to reproduce it
reliably.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


One way you can consistently recreate the issue is as follows:
1. Configure a module to use a (Global) library
2. Create a class that uses a class from the library configured in step #1
3. Compile the class
4. Open project settings and remove the library
5. Compile the class. The red underlining appears
6. Go back to project settings and re-add the library
7. You can then recompile the class, which now compiles fine, but the red underlining does not get removed.

While this is not a normal usage pattern, it is a way to consistently reproduce the issue. I discovered this pattern when opening an old project that used some obsolete global library definitions.

Like others, I have also experienced the issue under different circumstances, but am not sure of a consistent cause.

0
Comment actions Permalink

Not sure if it helps, but I've noticed that it's been occurring when the
code is initally red due to an out-of-date JAR file. When I update the JAR
(externally to IDEA) and then come back to IDEA, it scans the JAR, finds the
right stuff, and then compiles successfully. However, the file is still
marked as red.

Is there any debugging information that I could supply that'd help track
down this problem?

;ted

"Dmitry Jemerov" <yole@jetbrains.com> wrote in message
news:609b4cc98bf888ca49315d1b7362@news.jetbrains.com...

Hello Ted,

>
>> Is this a known problem? Not sure how to recreate this...exiting IDEA
>> and reloading the project makes the redness go away.
>

Yes, this is a known problem, but we haven't found a way to reproduce it
reliably.

>

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

>



0
Comment actions Permalink

Yep, I get this all the time with out-of-date JAR files as well.

0
Comment actions Permalink

I can easily reproduce on the latest EAP build.

1) Create new project
2) Add 2 modules which depend on one another.
3) Setup the dependency between them
4) Right click on the module that has the dependency on the other and choose
compile. IntelliJ will say it can't find the classes from the other module
and will highlight the files/folders in red
5) right click on the other module and compile. Go back to the first module
in step 4 and right click compile. It will now compile but have red lines
under the classes and folder still.



"Simon Knott" <no_reply@jetbrains.com> wrote in message
news:15601120.1204669508570.JavaMail.itn@is.intellij.net...

Yep, I get this all the time with out-of-date JAR files as well.


0
Comment actions Permalink


In my case it is import statement

import com.compay.MyClass // MyClass never exists in classpath or project

class Test {
}

try to compile the project, IDEA shows error on the import stmt. Remove
this import and compile the project. No errors while compilation but IDEA
still shows Red mark on this file.

-RT

I can easily reproduce on the latest EAP build.

1) Create new project
2) Add 2 modules which depend on one another.
3) Setup the dependency between them
4) Right click on the module that has the dependency on the other and
choose
compile. IntelliJ will say it can't find the classes from the other
module
and will highlight the files/folders in red
5) right click on the other module and compile. Go back to the first
module
in step 4 and right click compile. It will now compile but have red
lines
under the classes and folder still.
"Simon Knott" <no_reply@jetbrains.com> wrote in message
news:15601120.1204669508570.JavaMail.itn@is.intellij.net...

>> Yep, I get this all the time with out-of-date JAR files as well.
>>


0
Comment actions Permalink

I see this in 7744 (attempt to compile, get error, correct error, recompile), but I don't exactly rebuild - I use ant to rebuild and it doesn't go away. Closing and restart IDEA always seems to fix the problem. While less than ideal I do see that 7757 is available so I have a decent reason to restart this time.

0
Comment actions Permalink

Hello Quincy,

I see this in 7744 (attempt to compile, get error, correct error,
recompile), but I don't exactly rebuild - I use ant to rebuild and it
doesn't go away. Closing and restart IDEA always seems to fix the
problem. While less than ideal I do see that 7757 is available so I
have a decent reason to restart this time.


This problem is not fixed in build 7757 but should be fixed in 7782 (7.0.4
first EAP).

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

This is not completely fixed. I am running Selena Build 7860 and have a module dependency from one test tree (designated as green test, not blue src in module settings) to the test tree in another module. There was previously a correct red error in the editor before I created the module dependency, but after fixing it, the compile fails and it still shows as red in the project tree even though the editor is clean. I've cleaned out caches and restarted many times and the problem does not go away. However, when I go into the depended-upon module and designate the test tree as a blue src tree and then recompile, the problem disappears.

0
Comment actions Permalink

Hello all, and especially Dmitry, the Lead of Development who says that Intelij is  "Develop with Pleasure!".

I must say that this particular bug is a HUGE obstacle to "Develop with Pleasure!".

Every time I see it, it makes me want to uninstall Intelij. Seriously. I feel like an idiot when everything is clean but Intelij blocks me and draws thousand of red lines all over my code. And i see it quite a lot. I also can see that reports of this bug have been recorded since 2013.

Way to go.

1
Comment actions Permalink

I mostly had bad experiences with IntelliJ due to this stupid bug. Someone needs to make this IDE worth the money and time of a developer.

0
Comment actions Permalink

Hi @Officialdharam. This is quite an old thread and the issue initially reported has been fixed long ago. Could you please elaborate on your problem a bit more? Screenshots would be helpful to understand the problem. Do you use Maven/Gradle? Thanks.

0
Comment actions Permalink

In my environment this is centered around a file that exceeds the configured limit.  When I attempt to configure the limit higher, IDEA just locks up completely.  I am unable to move forward in the IDE right now.

Further, the file appears in the tree with a java file icon (that looks like a file coming out of a printer labeled J) and the extension .java is present, whereas all other java files in the same directory (and elsewhere) are marked with a circular icon with the letter C in it.

The file that exceeds size is also a generated file with only public static final int fields defined.

0
Comment actions Permalink

Hello,

What "limit" do you mean?

 

0
Comment actions Permalink

@Yaroslav Bedrov


idea.max.intellisense.filesize
0
Comment actions Permalink

What is your file size? What "filesize" value did you set?

0
Comment actions Permalink

@Yaroslav Bedrov

I doubled the default value from 2500 to 5000

0
Comment actions Permalink

Could you please create support request using "Submit a request" button at the top of this page and provide file example or logs folder zipped (https://intellij-support.jetbrains.com/hc/en-us/articles/207241085-Locating-IDE-log-files) after facing a freeze?

0

Please sign in to leave a comment.