FULL PRODUCT VERSION :
java version "1.6.0_23"
OpenJDK Runtime Environment (IcedTea6 1.11pre) (6b23~pre11-0ubuntu1.11.10.1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing)


ADDITIONAL OS VERSION INFORMATION :
Linux atitudem 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Windows Server 2008

A DESCRIPTION OF THE PROBLEM :
Compiling some Java sources with a folder on the classpath containing any class file with the exact size of 65520 (0x0fff0) bytes leaves javac spinning in a loop with high CPU usage and wihout terminating.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Create/find a class file with the file size of 65520 bytes let's call it A65520.class
2. Create any valid Java source file B.java and compile it with A65520.class on the classpath:
    javac -cp . B.java

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The javac application should terminate and have produced B.class.
ACTUAL -
The javac application never terminates and uses almost all CPU of one core.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
If a class file ends up being 65520 bytes large, do some refactoring or add a field or something resulting in a class file with different size.