-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
5.0u14
-
other
-
generic
OPERATING SYSTEM(S):
All - common code.
FULL JDK VERSION(S):
Present in sync.c versions up to and including 1.17 (Java 5)
DESCRIPTION:
In several places in the CMM sync.c code (from Kodak) unexpected errors are handled with "for(;;);" - which sends the system into a screaming loop.
These constructs cause compiler warnings and are poor programming practise. If a system encounters one for any reason we get no documentation or error messages - just an unresponsive system consuming all system CPU.
In sync.c version 1.17 the offending lines are:
* 673
* 688
* 728
* 845
* 857
An abort() would be a more useful way to cope with these conditions.
All - common code.
FULL JDK VERSION(S):
Present in sync.c versions up to and including 1.17 (Java 5)
DESCRIPTION:
In several places in the CMM sync.c code (from Kodak) unexpected errors are handled with "for(;;);" - which sends the system into a screaming loop.
These constructs cause compiler warnings and are poor programming practise. If a system encounters one for any reason we get no documentation or error messages - just an unresponsive system consuming all system CPU.
In sync.c version 1.17 the offending lines are:
* 673
* 688
* 728
* 845
* 857
An abort() would be a more useful way to cope with these conditions.
- duplicates
-
JDK-6640337 Infinite Loops as Error-Handling in CMM sync.c
- Open