#1917 new
Alex L

Noticed a small bug, probably will be easy fix

Reported by Alex L | May 5th, 2015 @ 07:29 AM | in 2.1 Release

There is a problem if you close out of the configuration window that you are first presented when launching jbidwatcher from the red x in the top right corner. The program window will close but the process will not terminate. If you launch task manager you will see a javaw.exe running that is the process of jbidwatcher using same amount of RAM as when the tool was open.

Basically clicking the red x will just close the windows but not terminate, just eating up a little bit of RAM, it is not a big deal but just something that can be fixed or cleaned up if you get to it.

I am using a windows 7 professional running Oracle java 1.8.

I have noticed this problem with java programs I am making myself. The way to fix it is where ever you are initializing the parts of the jframe (I am assuming that is what you are using for the window GUI parts) is just add an extra line that says basically you have to set the default, I dont know why it is doing this, I am fairly new to java so I don't know if it is a recent change in 1.8 or what.

setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);

Just figured I would let you know :)

No comments found

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins

People watching this ticket

Pages