Strange lock of Application with JFileChooser

[Magnus]

Hi,

I don't even know where to start looking for the error here :(

I have a tester that got a new app and as soon as he click on a button
that is to open a JFileChooser, the application locks, the CPU goes to
100% and it takes 2 minutes to get the Task-Manager. No HD-activites
could be noticed either.

This is where it gets strange, to me at least:
1) I have tried the app on 2 PCs - no problem.
2) It is the same standard code used on every older version of the app
for the last year (at least).
3) The tester tried to run an older version, we both know for sure did
work, and clicked another button, again that we know worked, to open a
JFileChooser - It locked?
4) Java has not been upgraded and no other software has been installed
on the PC.

He's using JRE 1.5 and I use JRE 1.5 & 1.4.

Anyone experienced anything similar? Any pointers where to start looking?

TIA

[Kevin Dean [TeamB]]

Post by Magnus
I have a tester that got a new app and as soon as he click on a button
that is to open a JFileChooser, the application locks, the CPU goes to
100% and it takes 2 minutes to get the Task-Manager. No HD-activites could
be noticed either.

First of all, as only his PC is doing it, the culprit is likely not your
application or Java but rather something on his PC. I have generally
found lockups like this to be related to network drives. If one of his
network drives is on a remote network, running anything that has to query
the drive list is going to lockup as the operating system attempts to
reauthenticate with the remote server. That's a place to start looking.
--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/

NEW WHITEPAPERS
Team Development with JBuilder and Borland Enterprise Server
Securing Borland Enterprise Server
http://www.datadevelopment.com/papers/index.html

Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html

[Magnus]

Post by Kevin Dean [TeamB]

Post by Magnus
I have a tester that got a new app and as soon as he click on a button
that is to open a JFileChooser, the application locks, the CPU goes to
100% and it takes 2 minutes to get the Task-Manager. No HD-activites
could be noticed either.

First of all, as only his PC is doing it, the culprit is likely not your
application or Java but rather something on his PC. I have generally
found lockups like this to be related to network drives. If one of his
network drives is on a remote network, running anything that has to
query the drive list is going to lockup as the operating system attempts
to reauthenticate with the remote server. That's a place to start looking.

Thanks Kevin for your input and I agree about the "probable cause".

Just a follow up:
- It is only on that PC
- It is still a problem
- We have not been able to find the network drive that cause this
- No problem open any directory from XP-Explorer
- We will continue to look