File Open dialog bug in 1.6.0_03

[nemonow]

I am using 1.6.0_03 under Win2K SP4 for a couple of apps and in both
cases I see a problem with the File Open dialog box. When put in
"details" mode the columns include "modified" which should be the file
date. But instead I see the file type. There is also no way to add
columns to this dialog. In a windows generated File Open dialog, I
can add or remove columns. So I have no way to sort the files in this
dialog by date.

Is this a known bug? Is it specific to Win2K or does it appear on all
Windows versions?

Is there a fix or work around for the application developer?

 

[Zig]

I am using 1.6.0_03 under Win2K SP4 for a couple of apps and in both
cases I see a problem with the File Open dialog box. When put in
"details" mode the columns include "modified" which should be the file
date. But instead I see the file type. There is also no way to add
columns to this dialog. In a windows generated File Open dialog, I
can add or remove columns. So I have no way to sort the files in this
dialog by date.

Is this a known bug? Is it specific to Win2K or does it appear on all
Windows versions?

Is there a fix or work around for the application developer?

Are you using FileDialog, or JFileChooser? If you are using one, have you
tried the other?

How many Win2k installs have you seen this behavior on? Have you tried
other VMs? (1.6.0_02, or 1.5.0_12)?

It probably wouldn't hurt to post a SSCE...

 

[nemonow]

Are you using FileDialog, or JFileChooser? If you are using one, have you
tried the other?

How many Win2k installs have you seen this behavior on? Have you tried
other VMs? (1.6.0_02, or 1.5.0_12)?

It probably wouldn't hurt to post a SSCE...

I am not the developer. I am a user at openstreetmap.org. I don't
have any other platforms to test this on and I don't know enough about
java to try the code change you suggested. The developer knows about
it, so I assume I am not the only one seeing it. For whatever reason
(likely the linux vs. MS thing) the developer doesn't see this as an
issue worthy of his time. I can understand that, but it is a bother
to me and it does seem to affect multiple apps (JOSM and cotoGPS). I
just thought it might be a known bug that will be fixed soon or that a
known workaround exists.

I'll pass your suggestion on to him to see if he will try it.

As to the SSCE, I assume that is a bug report. I don't have a clue
about where to begin with that. I'll be happy to do it if you tell me
where and how.

Thanks...

 

[Ramon F Herrera]

Is this a known bug? Is it specific to Win2K or does it appear on all
Windows versions?

It must be well known by now. I have reported it about a dozen times
(with dump data from different computers and applications). The bug is
present in Win2K and WinXP, at least.

Is there a fix or workaround for the application developer?

The only workaround is to downgrade to Java 1.5.

-Ramon

 

[Ramon F Herrera]

I am using 1.6.0_03 under Win2K SP4 for a couple of apps and in both
cases I see a problem with the File Open dialog box. When put in
"details" mode the columns include "modified" which should be the file
date. But instead I see the file type. There is also no way to add
columns to this dialog. In a windows generated File Open dialog, I
can add or remove columns. So I have no way to sort the files in this
dialog by date.

Is this a known bug? Is it specific to Win2K or does it appear on all
Windows versions?

Is there a fix or work around for the application developer?

Zig:

I found the posting below in the developer forums:

http://forum.java.sun.com

It seems to match your description perfectly. The only difference is
that you are running Win2K and the poster is running WinXP (no real
difference, really).

One can help but wonder whether Microsoft is playing dirty tricks
again...

-Ramon

-------------

Hi,

Has anyone else experienced this? I installed JDK6u3, and soon
thereafter, the file dialogs that various Java-based applications use
stopped working. This occurred with my own software, another program I
use, and a third program completely failed to load. If file dialogs
weren't being used, the programs worked fine.

The problem was fixed once I bit the bullet and downgraded to JDK
5u13.

Anyone else have this problem? I can't find any information on it...
I'm using Windows XP Pro, and also experienced this on two different
computers.

Thanks,
Wojciech

 

[Ramon F Herrera]

I am using 1.6.0_03 under Win2K SP4 for a couple of apps and in both
cases I see a problem with the File Open dialog box. When put in
"details" mode the columns include "modified" which should be the file
date. But instead I see the file type. There is also no way to add
columns to this dialog. In a windows generated File Open dialog, I
can add or remove columns. So I have no way to sort the files in this
dialog by date.

Is this a known bug? Is it specific to Win2K or does it appear on all
Windows versions?

Is there a fix or work around for the application developer?

nemonow:

I am so glad to find another fellow sufferer, or perhaps we should
call ourselves "victims of a bug" and start a support group.

Java 1.6 indeed crashes a lot. I have narrowed it down to the file
chooser dialog, and I am pretty sure the problem is related to Swing.
The problem is present in my two computers. A rather poor solution is
to downgrade to Java 1.5.

After "the various Java-based applications stop working" (actually
crashing) look for a file that looks like hs_errr_pid<xxx>.txt (the
'xxx' is the process ID number) and you may want to report it to
http://java.sun.com/webapps/bugreport/crash.jsp. That file can be
found in:

C:\Program Files\Java\jre1.6.0_03\bin
C:\Program Files\netbeans-5.5.1


Below are some of the occurrences, which I have reported to the
developers.

- The affected programs are both written by myself and from other
sources (Sun, for instance).

- There is a JavaThread "Swing-Shell" daemon and a
~RuntimeStub::resolve_opt_virtual_call involved.

- One of the applications that fails is the NetBeans 6beta2 installer,
as soon as I click on "Next"

- Another sure way to reproduce the problem is:
Start | Settings | Control Panel | Java Control Panel | Java | Java
Application Runtime Settings | View | Find | Next
(boom!)

-Ramon

 

[Lew]

How many Win2k installs have you seen this behavior on? Have you tried
other VMs? (1.6.0_02, or 1.5.0_12)?

Those VMs have a major security hole. 6u3 and 1.5.0_13 are the releases that
patched that hole.

 

[Lew]

It probably wouldn't hurt to post a SSCE [sic] ...

You should spell it right if you're introducing people to new concepts, else
they can't google it as effectively.

As to the SSCE, I assume that is a bug report.

If it hadn't been for the typo, you might have found
<http://www.physci.org/codes/sscce.html>

Don't assume. GIYF.

 

[nemonow]

It must be well known by now. I have reported it about a dozen times
(with dump data from different computers and applications). The bug is
present in Win2K and WinXP, at least.




The only workaround is to downgrade to Java 1.5.

Thanks for the info. So you are saying that this is a *new* problem
that started with 1.6? The whole version thing confuses me. There is
this version which I assume applies to the interface of the app to the
java run time? The java I downloaded from Sun is 6.3, which I assume
applies to the run time code itself?

The bug mentioned in the forum seems to be different since I don't see
a crash. I just see improper action in the file>open dialog box.

 

[Lew]

The java [sic] I downloaded from Sun is 6.3, which I assume
applies to the run time code itself?

No, you did not download Java 6.3, because there is no such version. What you
downloaded is Java 6, update 3, sometimes called 1.6.0_03.
<http://java.sun.com/javase/6/webnotes/version-6.html>

The version identifies the version of the compiler that generates the
bytecode, the version of the class file that holds the bytecode, and the
version of the JVM that runs the bytecode. I'm not clear on what you mean by
"the run time [sic] code itself".

 

[Ramon F Herrera]

> Thanks for the info. So you are saying that this is a
> *new* problem that started with 1.6?

Exactly. The problem is present in all versions of Java 1.6 (aka Java
6) and it is absent from all versions of Java 1.5 (aka Java 5).

The whole version thing confuses me. There is
this version which I assume applies to the interface of the app to the
java run time? The java I downloaded from Sun is 6.3, which I assume
applies to the run time code itself?

Hmm??

The bug mentioned in the forum seems to be different since I don't see
a crash. I just see improper action in the file>open dialog box.

What do you mean by "not seeing a crash"? There are no BSODs or
anything visible like that. The only evidence of the crash is a file
called hs_err_pid*.txt. Are you sure you don't have files like that
anywhere in your PC? Look here:

C:\Program Files\Java\jre1.6.0_03\bin

Look in the default directory were your application runs.

Have you tried this? Does it work for you?:

Start | Settings | Control Panel | Java Control Panel | Java | Java
Application Runtime Settings | View | Find | Next

Please try it out (request directed to any of you out there who are
running WinXP and Java 6) and report your findings.

-Ramon

 

[nemonow]

Exactly. The problem is present in all versions of Java 1.6 (aka Java
6) and it is absent from all versions of Java 1.5 (aka Java 5).


Hmm??

What you said... what is Jave 1.6 and Java 6, two names for the same
thing? That seems ridiculous. They must be describing two different
things that apply to the same software.

What do you mean by "not seeing a crash"? There are no BSODs or
anything visible like that. The only evidence of the crash is a file
called hs_err_pid*.txt. Are you sure you don't have files like that
anywhere in your PC? Look here:

C:\Program Files\Java\jre1.6.0_03\bin

Look in the default directory were your application runs.

Have you tried this? Does it work for you?:

Start | Settings | Control Panel | Java Control Panel | Java | Java
Application Runtime Settings | View | Find | Next

Please try it out (request directed to any of you out there who are
running WinXP and Java 6) and report your findings.

I'm not sure what I should be looking for. I don't see the
hs_err_pid*.txt in either the java directory or my application
directories. My control panel is a bit different. I found Control
Panel | Java and when I ran it, it opens a dialog labeled "Java
Control Panel". Inside I found an Application Runtime Settings button
which opens another dialog. I found View | Find | Next which seem to
search for the JRE. What do I do with this?

When I said I don't see a crash, I don't see the application lock or
vanish. Not since I upgraded to ver 1.6 or 6 or what ever it is.

 

[Ramon F Herrera]

What you said... what is Java 1.6 and Java 6, two names for the same
thing? That seems ridiculous. They must be describing two different
things that apply to the same software.

This is not the first time they do something like that. Solaris also
had some numerical changes and IIRC it was even more confusing.

I'm not sure what I should be looking for. I don't see the
hs_err_pid*.txt in either the java directory or my application
directories. My control panel is a bit different. I found Control
Panel | Java and when I ran it, it opens a dialog labeled "Java
Control Panel". Inside I found an Application Runtime Settings button
which opens another dialog. I found View | Find | Next which seem to
search for the JRE. What do I do with this?

When I said I don't see a crash, I don't see the application lock or
vanish. Not since I upgraded to ver 1.6 or 6 or what ever it is.

It seems that you are experiencing an entirely different bug. I should
have read your posting more carefully. The bug I am talking about
makes the application vanish, and it seems to be restricted to WinXP.

-Ramon

 

[Bent C Dalager]

What you said... what is Jave 1.6 and Java 6, two names for the same
thing? That seems ridiculous. They must be describing two different
things that apply to the same software.

I believe this is a reasonably accurate nutshell description of the
matter: Java 6 is the marketing name and Java 1.6 is the technical
name.

Sun does these things.

People who want to confuse you (further) will call it Java2 v6 or
Java2 v1.6 - the "Java2" bit appears to be fallout from the Java wars
of 2001.

Cheers,
Bent D

 

[Ramon F Herrera]

nemonow:

I am so glad to find another fellow sufferer, or perhaps we should
call ourselves "victims of a bug" and start a support group.

Java 1.6 indeed crashes a lot. I have narrowed it down to the file
chooser dialog, and I am pretty sure the problem is related to Swing.
The problem is present in my two computers. A rather poor solution is
to downgrade to Java 1.5.

After "the various Java-based applications stop working" (actually
crashing) look for a file that looks like hs_errr_pid<xxx>.txt (the
'xxx' is the process ID number) and you may want to report it tohttp://java.sun.com/webapps/bugreport/crash.jsp. That file can be
found in:

C:\Program Files\Java\jre1.6.0_03\bin
C:\Program Files\netbeans-5.5.1

Below are some of the occurrences, which I have reported to the
developers.

- The affected programs are both written by myself and from other
sources (Sun, for instance).

- There is a JavaThread "Swing-Shell" daemon and a
~RuntimeStub::resolve_opt_virtual_call involved.

- One of the applications that fails is the NetBeans 6beta2 installer,
as soon as I click on "Next"

- Another sure way to reproduce the problem is:
Start | Settings | Control Panel | Java Control Panel | Java | Java
Application Runtime Settings | View | Find | Next
(boom!)

-Ramon

This bug has been FIXED.

http://bugs.sun.com/view_bug.do?bug_id=6522704

Just download the early release JRE from https://jdk6.dev.java.net/

-Ramon

 

[Andrew Thompson]

...
I am not the developer. I am a user at openstreetmap.org.
... For whatever reason
(likely the linux vs. MS thing) the developer doesn't see this as an
issue worthy of his time. ...

It seems a waste of time if the developer will not support
their own product, but a 'workaround' for it would be to
launch the app. via. JWS and request versions of the
Java runtime that are not affected by the bug.

This would also require the developer to digitally sign the
application (A file chooser is not available to a sandboxed
app.).

I recommend you bounce the text of this message to
them, invite them to come here for further advice on JWS,
if interested, and if not, find yourself some software that
*is* supported.