Actions
Bug #3349
closedAssertionError thrown when FeatureKeys.MAX_COMPILED_CLASSES limit reached
Start date:
2017-07-13
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.8
Fix Committed on Branch:
9.8
Fixed in Maintenance Release:
Platforms:
Description
Reported by Gunther Rademacher:
An AssertionError is thrown when the MAX_COMPILED_CLASSES limit is reached and Java assertions are enabled.
Exception in thread "main" java.lang.AssertionError
at com.saxonica.ee.bytecode.util.CannotCompileException.<init>(CannotCompileException.java:26)
at com.saxonica.ee.bytecode.util.CompilerService.checkMaxClassesLimit(CompilerService.java:1308)
This is harsh as it was added for diagnostic purposes.
Updated by O'Neil Delpratt almost 7 years ago
- Status changed from New to Resolved
- Fix Committed on Branch 9.8 added
I have added code to prevent the use of the assertion for the condition of reaching the MAX_COMPILED_CLASSES. We now revert to the interpreted code.
Updated by O'Neil Delpratt almost 7 years ago
Fixed in the CompilerService and CannotCompileException classes.
Updated by O'Neil Delpratt over 6 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.8.0.4 added
Bug fix applied in the Saxon 9.8.0.4 maintenance release.
Please register to edit this issue
Actions