Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm having an issue that I'm hoping someone can help with. I'm working on netbook running WinXP Pro SP3, 1.6GHz & 1GB of RAM. I've got a relatively simple java program that I'm able to successfully compile and run on other computers (both XP and Win7), so I suspect my code is working fine--I've verified that all computers are running the same version of Java (build 1.7.0_02-b13).

For about the past week, I get maybe three or four compiles and runs at the command prompt (running CMD from within WinXp) before I hang with a blinking cursor after keying my command and pressing enter. If I shut down the command prompt window and restart it, I can compile and run the program just fine--again, pointing to an OS/environment issue rather than code.

The only system change I've made in the past week is to uninstall a Lexmark printer that I ditched a year ago, and removing/reinstalling Java. Oh, and an automatic Windows update... :\ I've used this netbook successfully for programming classes for the past year and a half.

Anyone familiar with this issue and know of some system tweaks to solve it? I suspect that memory may not be getting cleaned up when the java program quits...only when CMD closes, but don't know any tools to troubleshoot. Ideas?

share|improve this question
1  
Never seen or experienced that before, this is very strange. Are you using a script to compile and/or run your code? If so, could we see it? (Maybe the actual commands you run too.) Does your program manipulate stdin/stdout in interesting ways? –  Mat Apr 14 '12 at 13:28
    
@Mat: no scripts...just javac JavaProgram.java and java JavaProgram at the command prompt. I'm importing javax.swing.* and my class extends another...but it's a class project, so it's not terribly complex. –  dwwilson66 Apr 14 '12 at 13:34
add comment

1 Answer

up vote 0 down vote accepted

While I was never able to find an answer to this question, the problem stopped happening as soon as I was finished testing the particular program, which runs fine in the production environment. When I originally submitted the question, I didn't think to run some other programs to see if it was something with that particular one...but it appears that it was.

I'm chalking this one up to sunspot activity. :)

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.