Bug 1064 - High CPU usage with ROX-panel and focus follows mouse
Status: CLOSED INVALID
Alias: None
Product: Openbox
Classification: Unclassified
Component: general
Version: 3.0
Hardware: PC Linux
: P2 normal
Assignee: Mikachu
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2003-12-06 12:10 EST by frml
Modified: 2007-05-16 15:52:24 EDT
0 users

See Also:


Description frml 2003-12-06 12:10:44 EST 
Hi,

I've got a strange problem with rox (filemamanger) and the 'focus 
folows mouse' option in Openbox.

Everytime wenn I move the mouse over the rox-panel the CPU usage
increases up to 100%.

X consumes 40%, ROX and Openbox an average 25% each of the cpu time.

I've also posted this bug to ROX mailing list
Comment 1 Dana Jansens 2003-12-22 13:18:03 EST 
Sounds like an event storm.
Comment 2 Dana Jansens 2003-12-22 14:43:44 EST 
OK, here's the problem.

When ROX gets an EnterNotify event (mouse enters that little 2px or so edge), it
raises itself. This actually requests Openbox to raise it.

When Openbox raises or lowers a window, and it was not caused by a mouse action
(this is caused by rox requesting it!), then it grabs the mouse before
raising/lowering the window and releases it after. This is so that focus does
not move around unless you cause it explicitly with the mouse in FFM.

When Openbox grab/releases the mouse, ROX receives a LeaveNotify/EnterNotify
pair on its window, with the mode set to NotifyGrab/NotifyUngrab.

ROX does *not* ignore this Leave/Enter pair, and so it asks to be lowered, then
raised again. Openbox grab/releases again. Etc.

ROX needs to ignore grab related enter/leave notify events.