Bugs item #3595874, was opened at 2012-12-14 01:43 Message generated for change (Tracker Item Submitted) made by defaultxr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3595874...

Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: rendering (e.g. display) Group: linux Status: Open Resolution: None Priority: 5 Private: No Submitted By: defaultxr (defaultxr) Assigned to: Nobody/Anonymous (nobody) Summary: extremely high cpu usage when using GEM in a tiling wm

Initial Comment: I use a window manager called StumpWM, and the default behavior of the window manager is to maximize all windows within their "frame". when i try to open a gem window via the [gemwin] object, the window manager and GEM get stuck in a "resizing fight", with the window manager attempting to resize the GEM window, and GEM attempting to reset the size. it works fine if i use a floating window group (which does not cause the window manager to try resizing the window), but i prefer not to have to do that. it also works if i send a "dimen" message to [gemwin] with the precise dimensions that StumpWM will try to resize the window to, but if i attempt to split the window-frame, the problem comes back.

----------------------------------------------------------------------

You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3595874...