Menu

#440 High memory usage

Slowdown
open-accepted
8
2005-05-22
2004-10-13
James Cohen
No

I'm seeing really high memory usage and out of memory
exceptions being thrown.

JBidWatcher-0.9.5.jar
P4 2.8G
512MB RAM
j2re1.4.2_05

The errors were thrown with a multisnipe group of four
or 5 items and around 6 other auctions listed in the
current tab (but with no snipes assigned).

The application had been running for 8 or 9 hours.

If there's any further debug I can give you please let me
know.

Discussion

  • Morgan Schweers

    Morgan Schweers - 2005-05-22
    • priority: 5 --> 8
    • status: open --> open-accepted
     
  • Morgan Schweers

    Morgan Schweers - 2005-05-22

    Logged In: YES
    user_id=19745

    Greetings,
    At a guess, I'm going to presume Windows, as it sets a 64MB
    cap on Java processes.

    One thing to do, to see JBidwatcher's memory usage, is to add

    debug.memory=true

    to the JBidWatch.cfg file in:
    Documents and Settings/{Username}/.jbidwatcher
    or
    ~/.jbidwatcher
    or
    /Users/{username}/.jbidwatcher
    for Windows, Linux/FreeBSD/Solaris, and MacOSX respectively.

    Add that line while JBidwatcher is not running, then restart
    JBidwatcher, and you'll find a little box that says how much
    memory has been allocated to JBidwatcher, and how much it's
    using so far. (It will also allow you to forcibly 'garbage
    collect' JBidwatcher.)

    I'm leaving this open for now as a 'high memory' bug,
    although it's unlikely to ever get actually resolved. I'll
    make any updates about memory on this bug.

    -- Morgan Schweers, CyberFOX!

     

Log in to post a comment.