You can change Chainsaw to store each tab's events in a cyclic buffer - under the 'Current tab' menu, check the 'Use Cyclic' menu item.
The size of the cyclic buffer is a global application setting, and can be set from the 'View, Show application-wide preferences' menu - change the 'cyclic buffer size' value. If you are suggesting to make the cyclic buffer cycle within a range, it sounds like a good idea (less object churn): 'always display a minimum of X events. Once the number of events reaches Y, remove everything except for the most recent X events' Scott -----Original Message----- From: Sergio Traldi [mailto:[EMAIL PROTECTED] Sent: Mon 9/26/2005 7:53 AM To: [email protected] Subject: Chainsaw Error: java.lang.OutOfMemoryError Hi all I'm using the chainsaw v2 from the website launched with the Java Web Start (http://logging.apache.org/log4j/docs/webstart/chainsaw/chainsawWebStart.jnlp). I sent to chainsaw about 6.000.000 of log messages, and I saw the chainsaw received well until 5.600.000 messages. After that number it seems chainsaw is stuck, and then a java error of java.lang.OutOfMemoryError appears. Is there a parameter to set to avoid this problem? If I press the trash button in chainsaw visualization every n (n < 5.000.000) messages all works fine. Is there a way to delete automatically the messages every a fixed number of arrived messages (for example 2.000.000)? cheers Sergio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
