frozen windows

Godmar Back gback at cs.utah.edu
Fri Jan 8 17:52:09 PST 1999


 1.0b3's awt has several bugs, some of which cause it to deadlock
in the way you describe.  One of the bugs has been fixed in the current
CVS version, and Peter has fixes for the (known) others that will be
integrated with the next merge from TVT.

Also, the next version of kaffe won't silently deadlock anymore,
it will complain loudly when that happens.

	- Godmar

> 
> Kaffe 1.0.b3 :
> 
> I experience quite regularly frozen windows (of class Form). All of a
> sudden the client area of such a window no longer responds to mouse
> clicks and does no longer repaint() etc. Sorry to be so unspecific but
> I'm out of my depth here.
> 
> Maybe this list helps which shows the processes I started to test a
> client/server app. The frozen window belongs to PID 1895 (Client1)
> 
> 
>  FLAGS   UID   PID  PPID PRI  NI   SIZE   RSS WCHAN       STA TTY TIME
> COMMAND
> 
>    100     0   937   933   0   0   1212   684 read_chan   S   p0  0:00
> bash 
>    100     0  1094  1087   0   0   1212   684 wait4       S   p1  0:00
> bash 
>    100     0  1093  1088   0   0   1248   692 wait4       S   p2  0:00
> bash 
>    100     0  1895  1093   9   0  24868 16676 pipe_write  S   p2  3:07
> /usr/bin/Kaffe -ms 10m Client1 100 
>    100     0  1885  1094   0   0  13436  9516 do_select   S   p1  0:02
> /usr/bin/Kaffe -ms 10m DBManager TeamManager 
>    100     0  1114  1108   0   0   1212   684 read_chan   S   p3  0:00
> bash 
>    100     0  1116  1109  10   0   1212   688 wait4       S   p4  0:00
> bash 
> 100100     0  1928  1116  10   0   1012   404             R   p4  0:00
> ps -wl
> 
> 
> 



More information about the kaffe mailing list