JBW regularly freezes...
Brought to you by:
cyberfox
Menu
▾
▴
#484 JBW regularly freezes...
I'm still using my 10.3.6 and JBW used to work correctly until now.
I even ugraded my RAM and my OS works more freely.
But for a few days, JBW acted strangely. It freezed.
After the auctions are finished (won or lost), they remain in the
CURRENT tab, showing the date in red instead of the remaining
time.
JBW seems very busy: I often have the color beachball spinning
and preventing me to give orders to the program. I almost can't do
anything, so I try to quit. Before that, I watch in the dock and the
app seems ok. Then I try quiting withour success. I watch again in
the dock and JBW is marked as "blocked". So I have to force quit. I
restart it and everything is ok.
I'm not sure JBW could go on working well in this state: I didn't
take the risk on a snipe. But I really don't think so.
This happened after an auction already bided finished, and another
time after a snipe. There were 4 or 5 auctions finished but still in
the current tab.
The first time it happened, I thought I had too many auctions for
JBW to handle: about 50. I have about 170 finished auctions in the
other tabs.
golgoth128@freesurf.fr
P.S. There is no error log file in the ".jbidwatcher" folder
Logged In: NO
This is happening to me too!
Logged In: NO
Apparently, this bug happens for no reason: even when no auction has
just been finished.
It's when I let JBW running a certain amount of time, then you can do
nothing with it except force quit.
golgoth128@freesurf.fr
Logged In: YES
user_id=607512
This is happening to me all the time on Windows 2000
professional with Java 1.4.2. It's been happening for a
while, but seems to have gotten worse over time. I think it
has to do with the size of the auction file. Are you using a
DOM-based XML parser? My auction .xml file is just a little
> 2MB. I think that Xerces has problems with larger files (>
2MB). I've tried moving the completed auctions to other
filders, but that doesn't seem to help (I guess the other
folders are stored in the same file).
Some symptoms:
Completed auctions do not move to the completed folder.
GUI response to some actions but not others:
Cannot close JBidWatcher. from the file menu or the window X
widget.
Save usually pops up a little window which must be OK'd out
of, but when JBW enters this 'freeze' up mode, the Save
control will stay depressed, and after 2-3 minutes will go
back to default (undepressed) mode, but the windows does not
pop up.
Update auction does not work.
SJBW still responds to menu actions: Configure, Get Info,
Delete Auction, Add Auction, Help Window, About Info window
still pop up.
Hope this helps, great software, but I haven't seen an
update in months. Could you use some help?
Logged In: NO
This problem also occures on my computer!
Even with 14 watches...
Logged In: YES
user_id=19745
Greetings,
I have just completed a move to Seattle, and finally have my
primary development systems up and running again, just today.
Coming up to speed at my new job, and situating myself in my new
apartment, with fiancee and cat, all has eaten up every available
cycle of my time until just recently. With my primary dev
environment back up (and not rebooting every 5 minutes!), I'm
able to start to address some of the problems people have been
reporting.
I've been trying to debug with one hand tied behind my back,
effectively, recently. Hopefully with the new setup, and
everything coming live, I'll be better able to respond and fix
problems.
I apologize for my awful response time, recently. Ever since
mid-February, I've been effectively offline. I barely managed
the 0.9.6 release due to eBay's change at one of the worst times
for me in terms of net access, and it looks like I overlooked a
few things in the process. I intend to try and fix those up, and
start on older bugs.
-- Morgan Schweers, CyberFOX!
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!