search

steveonjava / widgetfx

Automatically exported from code.google.com/p/widgetfx
BSD 3-Clause "New" or "Revised" License
2 stars 1 forks source link

Memory leak #48

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run WidgetFx on Windows XP with 3GB RAM
2. Wait
3. Memory usage for WidgetFX with the clock widget and news feed widget 
exceeds half a gigabyte

What is the expected output?
Memory usage should be lower - 64MB should be plenty

What do you see instead?
TaskManager reports WidgetFx using significantly more memory than NetBeans, 
easily consuming more RAM than any other application I have ever run.
Perhaps all that is needed is a more conservative setting for the max heap?

What version of the product are you using?
1.1
On what operating system?
Windows XP SP3

Please provide any additional information below.
3GB (really 4, but it's 32-bit windows and it can't handle 4)

Original issue reported on code.google.com by swpal...@gmail.com on 20 Mar 2009 at 12:55

GoogleCodeExporter commented 9 years ago 
WidgetFx 1.2.1 still has this problem.. at startup I get this:

... thousands of lines like these...
30-Jun-2009 3:06:34 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45166,localport=59042]
30-Jun-2009 3:06:34 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45167,localport=59056]
30-Jun-2009 3:06:34 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45168,localport=59057]
30-Jun-2009 3:06:34 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45169,localport=59059]
30-Jun-2009 3:06:34 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45170,localport=59061]
30-Jun-2009 3:06:34 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45171,localport=59062]
30-Jun-2009 3:06:34 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45172,localport=59063]
30-Jun-2009 3:06:34 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45173,localport=59068]
30-Jun-2009 3:06:35 PM org.widgetfx.communication.CommunicationSender <init>
INFO: CommunicationSender hooked up to socket = 
Socket[addr=localhost/127.0.0.1,port=45174,localport=59070]
Exception in thread "Communication Server Search Thread" 
java.lang.OutOfMemoryError: Java heap space
    at java.io.BufferedWriter.<init>(Unknown Source)
    at java.io.BufferedWriter.<init>(Unknown Source)
    at java.io.PrintWriter.<init>(Unknown Source)
    at org.widgetfx.communication.CommunicationSender.<init>(CommunicationSender.java:52)
    at org.widgetfx.communication.CommunicationManager$ServerStartThread.run(CommunicationManager.java:115)
    at java.lang.Thread.run(Unknown Source)
Exception in thread "Thread-5" java.lang.NullPointerException
    at com.sun.deploy.si.SingleInstanceImpl$SingleInstanceServer$2.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.deploy.si.SingleInstanceImpl$SingleInstanceServer.run(Unknown Source)

And the process is using 512MB of ram to show a clock and a news feed.

Original comment by swpal...@gmail.com on 30 Jun 2009 at 7:15

GoogleCodeExporter commented 9 years ago 
Inter dock communication mechanism was looping in some circumstances.

Original comment by ke...@widgetfx.org on 25 Oct 2009 at 11:34