https://bugs.documentfoundation.org/show_bug.cgi?id=170740
--- Comment #13 from [email protected] <[email protected]> --- So odd; I can reliably reproduce on 26.2 (can't upgrade yet cause I gotta clear space on this 256GB machine). It definitely seems timing related; after adding a bunch of debug printfs I can trigger with the first window; previously it would take a couple. I have 'Related: tdf#155092 don't rely on cached "in live resize" value' applied BTW. Anyway, it *looks* like we're getting stuck in DoYield() and repeatedly dequeuing the same two events over and over after we start live-resize: ###### DoYield: event 0x8b8ff5740 NSEvent: type=LMouseUp loc=(398.516,727.176) time=499443.1 flags=0x80020 win=0x8b359cc80 winNum=41501 ctxt=0x0 evNum=19185 click=0 buttonNumber=0 pressure=0 deviceID:0x200000000000029 subtype=NSEventSubtypeTouch ###### DoYield: event 0x8b8ff5680 NSEvent: type=LMouseUp loc=(398.516,727.176) time=499443.1 flags=0x80020 win=0x8b359cc80 winNum=41501 ctxt=0x0 evNum=19185 click=0 buttonNumber=0 pressure=0 deviceID:0x200000000000029 subtype=NSEventSubtypeTouch [aside: I'm printing pEvent with %p and [pEvent description] here and only ever get these two pEvent pointer values out of it... always same [description] but pointer values switch off] This seems to verify your theory that we're flooding the queue. In the bad case, when we hang, I never see [windowDidEndLiveResize] get called. Setting queueDispatchTimerEvent( false ); doesn't change anything for me. -- You are receiving this mail because: You are the assignee for the bug.
