#902 Random crashes. No errors.

[Nathan H]

I love the program, but it just isn't reliable! I am
currently running 1.0Pre6. The program tends to shut
itself off after a while. I've never actually been at
my computer when this happens, but sometimes after I've
gone off and done something else, the program isn't
there. Since I don't use it for simple bidding, only
for sniping, this just doesn't work.

SourceForge ID: digital_pioneer
E-Mail: digitalpioneer@gmail.com

[Morgan Schweers]

Logged In: YES
user_id=19745
Originator: NO

Greetings,
Bugs filed before 1.0 and bugs without responders are being juggled in terms of priority (9 is highest priority). I'm raising bugs filed with a submitter, post-1.0 to P6. Bugs which are filed post-1.0, but without a submitter are P5. Before 1.0 bugs with a submitter are becoming P4, and pre-1.0 bugs without a submitter name become P3.

If the bug is still relevant, and has a watcher (i.e. you got notified when I changed this bug), feel free to bubble it back up again.

Email addresses in bugs are great, but I can't always respond via email. Sometimes, especially for duplicate bugs, I use automated tools (like I'm doing right now) to change status on a large number of items at once.

Thanks for your patience, while I try to pare back the bug list to what may actually still be in the program.

-- Morgan Schweers, CyberFOX!

[Nathan H]

Logged In: YES
user_id=1414442
Originator: YES

Ehh, yeah, this is rather old. I got notified, but I don't know if it's still an issue. JBidwatcher doesn't appear to be in my APT repos, and installing manually has always been a nightmare. Once I spent a few weeks before giving up entirely.

[Morgan Schweers]

Logged In: YES
user_id=19745
Originator: NO

Greetings,
Right now I'm mostly just triaging to get the bug count under control, so I can figure out what needs to get into the next minor version.

Running JBidwatcher manually should be a matter of having the Sun Java runtime, and the JBidwatcher-1.0.jar file, and launching it with:
java -Xmx512m -jar JBidwatcher-1.0.jar

However, the crashes are more likely to be Java runtime issues... There's really nothing that will cause JBidwatcher to exit/crash on its own. Usually when the Sun Java runtime crashes, it leaves a file lying around (named like 'hs_pid' or something like that). This is usually due to an incompatibility of some sort.

Also very, very common is trying to use the gcj GNU toolchain instead of the actual Sun Java version. That doesn't work, because gcj isn't completely Java compatible.

Sorry to hear it was so difficult.

-- Morgan Schweers, CyberFOX!

[Nathan H]

Logged In: YES
user_id=1414442
Originator: YES

Perhaps I failed to note, that problem occurred in the windoze version. When I got Linux, it didn't work at all. As for using gcj vs. actual Java, I'm not sure. I saw gcj in APT, and since installing Java from APT is also usually a nightmare, I may have tried gcj instead. If I get desperate, I'll just use the old version that shipped in my distro. :)