Re: (timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-28 Thread Adam Jackson
On Mon, 2017-02-20 at 10:55 +0100, Daniel Martin wrote: > What happens is: > - ServertimeBlockHandler() forwards a _big_ unsigned timeout to > AdjustWaitForDelay() > - AdjustWaitForDelay() takes this _big_ unsigned as int and it becomes > a negative value This, I think, is where things start to g

Re: (timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-22 Thread Daniel Martin
Am 22.02.2017 11:24 schrieb "Daniel Martin" : On 21 February 2017 at 17:48, walter harms wrote: > Am 20.02.2017 10:55, schrieb Daniel Martin: >> What happens is: >> - ServertimeBlockHandler() forwards a _big_ unsigned timeout to >> AdjustWaitForDelay() >> - AdjustWaitForDelay() takes this _big_ u

Re: (timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-22 Thread Daniel Martin
On 21 February 2017 at 17:48, walter harms wrote: > Am 20.02.2017 10:55, schrieb Daniel Martin: >> What happens is: >> - ServertimeBlockHandler() forwards a _big_ unsigned timeout to >> AdjustWaitForDelay() >> - AdjustWaitForDelay() takes this _big_ unsigned as int and it becomes >> a negative val

Re: (timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-22 Thread walter harms
Am 21.02.2017 20:28, schrieb Mihail Konev: > On Tue, Feb 21, 2017 at 05:48:19PM +0100, walter harms wrote: >>> >> >> XSyncValueSubtract is doing as expected, >> XSyncValue is the simulation of 64bitvalues on 32bit. >> see this in hex: >> 10001 >> -2 >> 0 = 4294967295 i

Re: (timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-21 Thread Mihail Konev
On Wed, Feb 22, 2017 at 12:28:19AM +0500, Mihail Konev wrote: > > E.g. there is a typo in XSyncValue.lo definition - it should be uint > instead. Also wrong, the entire post was wrong, it was typo in my source. Mihail ___ xorg-devel@lists.x.org: X.Org

Re: (timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-21 Thread Mihail Konev
On Wed, Feb 22, 2017 at 12:28:19AM +0500, Mihail Konev wrote: > > Kind of - it errorneously returns > > 1 0001 > -0 0002 > 1 > Oh. This shouldn't matter in this case, as only is used. Offtop, sorry. Mihail ___ xorg-de

Re: (timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-21 Thread Mihail Konev
On Tue, Feb 21, 2017 at 05:48:19PM +0100, walter harms wrote: > > > > XSyncValueSubtract is doing as expected, > XSyncValue is the simulation of 64bitvalues on 32bit. > see this in hex: > 10001 > -2 > 0 = 4294967295 in .lo > Kind of - it errorneously returns 1

Re: (timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-21 Thread walter harms
Am 20.02.2017 10:55, schrieb Daniel Martin: > Hi everyone, > > I've got a Qt5 client, which receives mouse input only and freezes > soon and often. It gets stuck waiting for a reply from the server. > Pressing a none-modifier key releases the lock and the client > continues as normal until the n

(timeout in ms vs. XSyncValueSubtract) Frozen client, found cause, need advise for fix

2017-02-20 Thread Daniel Martin
Hi everyone, I've got a Qt5 client, which receives mouse input only and freezes soon and often. It gets stuck waiting for a reply from the server. Pressing a none-modifier key releases the lock and the client continues as normal until the next freeze. I've traced the bug down to a regression impl