It's worth to resolve till 3.5 if situation permits.

Brute force tests are not still able to reproduce it.

There is also a workaround, to invoke Reload document action.

For me this 100% reproducible under the following fairly normal and
clean conditions:

Build 200303131400
Win98
JDK1.4.1

- Have 2 projects, P1 and P2.
- In the project tab, P1 and P2 each have their own file systems, not
overlapping (normal situation).
- In the file systems tab, P1 and P2 share some of the file systems
(normal situation, don't know if this is necessary for failure).
- P1 is the project we are interested in. Open P1 and re-build the
code completion databases for all file systems in and check that it
works (it does work in my case).
- Switch to P2 and back to P1
- Try "Go to class" [Alt+Shift+O]

Result: The code completion does not work at all although it was
re-built during the same session a few minutes earlier.

Quite annoying.

Bernard you have uncovered it for Java sources. I'll fill new issue
for XML documents.

code completion is handled by editor module.

Bernard,

it could be the effect of the issue #31974
During project switching the parser DB was deleted. Thus, if you
returned to the project P1 again no parser DB files are available.
Although the parsing would start automaticaly, the databases will not
be available immediately after project P1 restore. Please, verify, if
I am right. Perform your reproduction steps and then look at your
<user dir> system/ParserDB folder, whether the parserdb files are
there. You can also use Tools/Code Completion Database Manager.
The fix of 31974 should fix this problem.

Martin,

I made the test as you suggested. It works now.

In fact I could not detect any code completion failure lately except a
reproducible case that is documented in issue 33515.
I made a testcase for that so hopefully fixing it is easy enough.

OK, resolving as worksforme. If you reproduce the issue again, please
reopen it.
Thanks.