Bug 9873

Summary: String.getBytes() garbles long strings, devours memory
Product: [Retired] Red Hat Linux Reporter: John Stracke <francis+rh+bugzilla>
Component: kaffeAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6.1CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://impp.research.ecal.com/java-model/kaffe-bug.html#getBytes
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-04-11 14:41:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Stracke 2000-02-29 23:41:52 UTC 
String.getBytes() has some weird bug where, if the string is over 1024
characters (or perhaps it's if the output is over 1024 bytes), it
garbles the output, makes it longer than it's supposed to be, and, for
strings over about 2048 characters, consumes vast amounts of CPU and
memory.  This has previously been reported to the Kaffe developers,
but they weren't able to replicate it.

The URL above has more details, a fix, and a link to the Kaffe bug-tracking
system where I also reported the bug.

I'm marking Severity as "high" because it does cause crashes.  Converting
an 1800-character string to bytes maxed out my memory (it took up something
over 32M) and choked my system to a crawl until it ran out of memory and
stopped.
Comment 1 Bill Nottingham 2000-04-11 14:41:59 UTC 
Fixed in kaffe-1.0.5-4. Thanks for the patch!