Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.lang.java.programmer
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Crash in Java 1.6.0_13 ImageIO PNG decoder (and possibly later versions) loading large interlaced PNGs with low memory
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Fredrik Jonson  
View profile  
 More options Nov 12 2012, 4:37 am
Newsgroups: comp.lang.java.programmer
From: Fredrik Jonson <fred...@jonson.org>
Date: 12 Nov 2012 09:37:16 GMT
Local: Mon, Nov 12 2012 4:37 am
Subject: Re: Crash in Java 1.6.0_13 ImageIO PNG decoder (and possibly later versions) loading large interlaced PNGs with low memory
Print | View thread | Show original | Report this message | Find messages by this author

In <k7pubs$rf...@news.mixmin.net> dy/dx wrote:
>  Using Java 1.6.0_13 -server -Xmx1100M what do you get if you run this code?

>  [...] I don't feel like going to a huge effort downloading a hundred megs of
>  later-Java-version, installing it, rebooting, fixing everything I'd need to
>  fix to make stuff use the later version, fixing broken links because the
>  binary pathname changed, and so forth, only to find out that the bug's
>  still there in the current version. :)

Please confirm that your internet connection is a 110 baud telex line on
Antarctica, and that you need to copy every byte by hand from the telprinter
paper to your terminal prompt to write them to disk. I'd be happy to assist if
I knew downloading 70 - not a couple of hundred - megabytes was a substantial
chore for you.

Also, tell me you're not running a 6u13 based service that exposed to the
internet? There are remotely triggerable DOS issues that has been resolved
since u13. The latest patch release is update 37, that's a whopping 24
security and stability improving patch releases ahead of your environment.

Besides, if your source code, build system, and service configuration is so
fragile it requires several hours of work just to upgrade the JDK, I recommend
that you take some time to fix that. Changing your $PATH and $JAVA_HOME
variables shouldn't be that much work. And while you're at it, consider
upgrading to JDK 7, as JDK 6 (non-for-pay) has a scheduled EOL in November 2012.

http://www.oracle.com/technetwork/java/eol-135779.html
https://blogs.oracle.com/henrik/entry/updated_java_6_eol_date

--
Fredrik Jonson


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google