Hi Jon, further testings show the issue is related to GNOME. XWin still crashed
after I started GNOME-SESSION and waited for some time without bringing up
any apps. I',m able to ssh to the Ubuntu box and bring up xterm or firefox and
do some work without any problems. Since you can't even s
On 03/11/2009 23:34, ERIC HO wrote:
Hi Jon, the crash is not caused by doing some specific action or looking at
specific pages in firefox. Sometimes I sit on the Firefox screen and the
cash happens. I ssh to the the remote Ubuntu Box and start up a
gnome-session there back to my display.
Over
Reverts the change which makes parented windows non-resizeable
Because this was trying to do something which we should be doing, as an
alternative we
try checking WM_NORMAL_HINTS for windows which shouldn't be resizable
If a window has a maximum size specified, no maximize box
If a window has a
Charles Wilson wrote:
[...]
AFAICT, the "cure" for all of these problems is worse than the disease
-- and the only *total* fix is for the main thread to always join()
the worker. Which is precisely what we want to avoid.
ACK and thanx for the explanations.
Ciao
Lothar
--
Unsubscrib
On 13/11/2009 13:06, Csaba Raduly wrote:
In the process of switching over to 1.7, I started running its X
server (instead of the X server of 1.5). A few days later I noticed
that some Eclipse windows (e.g. the Find dialog, the
Project->Properties, the Window->Preferences, etc.) can not be resized
Lothar Brendel wrote:
> Ok, this can be cured by
>
>if (pthread_cond_timedwait (&cv_xopenOK, &mtx_xopenOK, &then) ==
> ETIMEDOUT) {
> xopenOK = XSERV_TIMEDOUT; /* it's okay, we have the mutex */
> xopenTrying = 0; /* allow open_display() to give up */
> + pthread_mutex_unlock(&
Lothar Brendel wrote:
[...]
The
failure doesn't really harm, but we can be less dirty by checking the
result of pthread_mutex_unlock(), cf. the new patch.
Correction: I meant the result of pthread_mutex_lock() (in open_display()).
Ciao
Lothar
--
Unsubscribe info: http://cygwin.
Charles Wilson wrote:
[...]
The call to XOpenDisplay can take up to 12 seconds. Suppose the main
thread times out after say 5 seconds, and then just after that we
have a *successful* return in the worker thread. The worker thread
tries to get the mutex:
+ (*(data->xclosedis))(dpy);
+