• OpenProblems

Open Problems

This page lists problems that will need to be addressed sooner or later.

The most urgent issues are marked with priority icons ( , , ...).

Correctness

• KnownMauveFails - lists mauve fails with known reasons

• ThreadsafePatchers

• VeryLargeObjects

• DisplacementOverflows

• ExceptionHandlers - There is a problem when code falls through into an exception handler.

• SynchronousThreadCleanup

• OpenProblems/ExoticCfg

• LibraryCallsReview

• LoadingConstraintsReview

• DumpMemoryErrorHandling

• MemoryLeaks

Conformance

• WeakReferences

• BestEffortFinalization

• ClassUnloading (Note: Class unloading is called an optimization in the Java specification and required to be transparent, so this might also be viewed as a performance - instead of conformance - issue.)

Java 1.5 Conformance

• sun.misc.Unsafe, twisti implemented most but some are still missing.

Java 1.6 Conformance

• StackMaps

Performance

• FutexSystemTime - maybe these were caused by timed wait overflows

• MethodInlining

• ThinLocks - should be inlined

• GarbageCollectorTuning

• StacktraceTuning

• NotClearingMemory

• DirectCalls

• ClassNumbering

Enhancement

• StoppingThreads: for JVMTI to be useful we will need stopworld/stopping single threads

Build System / Source Tree

• include conditional sources in EXTRA_DIST?

• BackportingBranch: currently no issue as CACAO 0.96 works with Classpath 0.91.

Minor Issues

• option variables (like useinlining) should only be defined if the feature is enabled. (And useinlining should be opt_inlining).

• AbstractMethodErrors (see AbstractMethods) would be nicer with the name of the method in the error message.