Odd log and out of memory issues...

swpalmer

unread,

May 12, 2009, 9:46:18 AM5/12/09

to WidgetFX Users

Stephen Chin

unread,

May 13, 2009, 8:40:04 AM5/13/09

to widgetf...@googlegroups.com

It looks like the inter-process dragging support went crazy connecting
to itself. I have seen this happen once before, but wasn't able to
reproduce it.

Please file a bug on the issue tracker with as much detail as you have:
http://code.google.com/p/widgetfx/issues/list

My guess is that this is a race condition that is hard to trigger
normally, so I will spend some time making sure that the threading logic
is thoroughly reviewed before the next release.

Cheers,
--Steve

On 5/12/2009 6:46 AM, swpalmer wrote:
> Something is horribly wrong with WidgetFX or one of the Widets... I
> had the Java logging feature turned on and this is what the log showed
> when I restarted my computer this morning...
>

--
--Steve
blog: http://steveonjava.com/

swpalmer

unread,

Jun 30, 2009, 3:18:17 PM6/30/09

to WidgetFX Users

This is still a problem (Issue # 48)

It happens more frequently than not. What can I do to help?

> smime.p7s
> 4KViewDownload

Keith

unread,

Jul 1, 2009, 1:01:38 AM7/1/09

to WidgetFX Users

could you maybe run a netstat before opening WidgetFX and with all
other non-essential apps closed and post the results?

other than that, maybe we can setup up a version in beta with some
debug code in it for you to run.

swpalmer

unread,

Jul 6, 2009, 11:33:24 AM7/6/09

to WidgetFX Users

Active Connections

Proto Local Address Foreign Address State
TCP scott2:1043 localhost:32001 ESTABLISHED
TCP scott2:1044 localhost:32000 ESTABLISHED
TCP scott2:5152 localhost:37679 CLOSE_WAIT
TCP scott2:28893 localhost:30606 CLOSE_WAIT
TCP scott2:30606 localhost:37501 ESTABLISHED
TCP scott2:30655 localhost:30606 CLOSE_WAIT
TCP scott2:32000 localhost:1044 ESTABLISHED
TCP scott2:32001 localhost:1043 ESTABLISHED
TCP scott2:37014 localhost:30606 CLOSE_WAIT
TCP scott2:37020 localhost:30606 CLOSE_WAIT
TCP scott2:37341 localhost:30606 CLOSE_WAIT
TCP scott2:37472 localhost:30606 CLOSE_WAIT
TCP scott2:37501 localhost:30606 ESTABLISHED
TCP scott2:37775 localhost:30606 CLOSE_WAIT
TCP scott2:37038 server1.companyname.local:netbios-ssn
ESTABLI
SHED
TCP scott2:37506 server2.companyname.local:microsoft-
ds ESTABLIS
HED
TCP scott2:37923 server3.companyname.local:epmap
ESTABLISHED
TCP scott2:37924 server3.companyname.local:1025
ESTABLISHED

That's the output of netstat before launching WidgetFx..
When I launched WidgetFX it tried several thousand ports ending with
out-of-memory.. and then showed the WidgetFX UI.
...
6-Jul-2009 11:29:22 AM org.widgetfx.communication.CommunicationSender
<init>
INFO: CommunicationSender hooked up to socket = Socket[addr=localhost/
127.0.0.1,port=45237,localport=58622]
Exception in thread "AWT-EventQueue-1" java.lang.OutOfMemoryError:
Java heap space
6-Jul-2009 11:29:22 AM org.widgetfx.communication.CommunicationSender
<init>
INFO: CommunicationSender hooked up to socket = Socket[addr=localhost/
127.0.0.1,port=45238,localport=58626]
6-Jul-2009 11:29:22 AM org.widgetfx.communication.CommunicationSender
<init>
INFO: CommunicationSender hooked up to socket = Socket[addr=localhost/
127.0.0.1,port=45239,localport=58628]
Exception in thread "Communication Server Search Thread"
java.lang.OutOfMemoryError: Java heap space
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)

This only happens consistently on my work computer, at home (Windows 7
64-bit) I can't reproduce it.

Scott

swpalmer

unread,

Jul 8, 2009, 2:18:41 PM7/8/09

to WidgetFX Users

Ready for a debug build...

Keith

unread,

Jul 9, 2009, 1:51:46 AM7/9/09

to WidgetFX Users

While going in and adding some debug code I think I found the issue.
What do you get in you console output immediately on startup after:

Starting WidgetFX server on port xxxxxx

or do you even get that?

Keith

unread,

Jul 9, 2009, 2:22:46 AM7/9/09

to WidgetFX Users

Also, make sure WidgetFX (javaw.exe) can open port 34900. Your
firewall may be blocking it and I suspect this is the trigger of the
problem. I believe I have a fix ready to handle the error condition
better, but hopefully this will get you running quicker.

swpalmer

unread,

Jul 9, 2009, 2:21:12 PM7/9/09

to WidgetFX Users

No, I don't see that. Here's the full output.. the "..." are just
thousands of lines where the port numbers are increasing by one on
each line.

Java Web Start 1.6.0_14
Using JRE version 1.6.0_14-b08 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\scott.palmer
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
0-5: set trace level to <n>
----------------------------------------------------
Configuration directory location is: "C:\Documents and Settings
\scott.palmer\.WidgetFX"
9-Jul-2009 2:16:19 PM org.widgetfx.communication.CommunicationSender