... that deadlock is the GLMark2Test hang
<RAOF> Hm. That seems like odd behaviour. Why do you think it causes a deadlock?
<duflu> You can reallocate, but only at limited safe points in the lifecycle, which are not the same points we want to drop at
<duflu> RAOF: Because glmark2 freezes and both client and server are left idle waiting for each other
<duflu> Same theme as other bugs I'm fixing
<RAOF> Huh, I'm surprised.
<duflu> Me too, but happy to not have an unbounded buffer queue too
<RAOF> Eh.
<RAOF> As a practical matter we kinda need one.
<RAOF> Or, rather, we need at least one per monitor plus one for the client
<duflu> RAOF: Actually it's not entirely linear. Not simple, but if all monitors have the same frame rate then max two compositor buffers.
<duflu> Or max three with bypass multimonitors
<duflu> Or more with very slow refreshing monitors
<duflu> But fortunately not linear with number of monitors
<duflu> I'm really trying to avoid being asked to rewrite BufferQueue at the same time as the bug fxies
<duflu> fixes
<duflu> RAOF: To answer your earlier question; dropping frames in the wrong place results in us trying to send more exchange_buffer replies than we got requests, so that's an issue
<duflu> Oh very weird. I'm seeing two compositor buffers held simultaneously on Android
<duflu> is that overlays?
<duflu> alf: Why is the jellyfish (glmark2) so much smoother on a phone than desktop?
<duflu> alf__, ^
<alf__> duflu: it's smooth on my desktop :)
<duflu> alf__: I mean the vertices
<duflu> I've never found a desktop where it was smooth
<duflu> But on mako I can see what it's meant to look like
<alf__> duflu: Not sure what you mean... are you referring to e.g. the tentacles parts appearing to form corners?
<duflu> alf__: Yeah but the body particularly
<duflu> Like there's much higher mesh detail on the phone than
... that deadlock is the GLMark2Test hang 
 < RAOF > Hm. That seems like odd behaviour. Why do you remember it cause a deadlock? 
 < duflu > You can reallocate, but only at limited dependable points in the lifecycle, which are not the same points we desire to devolve at 
 < duflu > RAOF: Because glmark2 freezes and both client and server are left dead waiting for each other 
 < duflu > like theme as other bugs I'm fixing 
 < RAOF > Huh, I'm surprised. 
 < duflu > Me too, but happy to not have an boundless buffer queue too 
 < RAOF > Eh. 
 < RAOF > As a practical topic we kinda need one. 
 < RAOF > Or, rather, we need at least one per monitor plus one for the customer 
 < duflu > RAOF: Actually it's not entirely linear. Not simple, but if all monitors have the like frame rate then max two compositor buffers. 
 < duflu > Or max three with bypass multimonitors 
 < duflu > Or more with very slow refreshing monitor 
 < duflu > But fortunately not linear with number of monitors 
 < duflu > I'm really trying to avoid being asked to rewrite BufferQueue at the same time as the bug fxies 
 < duflu > fixes 
 < duflu > RAOF: To suffice your early question; spend skeletal system in the wrong place result in us trying to send more exchange_buffer replies than we got request, so that's an issue 
 < duflu > Oh very weird. I'm seeing two compositor buffers held simultaneously on Android 
 < duflu > is that overlays? 
 < duflu > alf: Why is the jellyfish (glmark2) then much smoother on a phone than desktop? 
 < duflu > alf _ _, ^ 
 < alf _ _ > duflu: it's legato on my desktop :) 
 < duflu > alf _ _: I entail the vertices 
 < duflu > I've never found a desktop where it was smooth 
 < duflu > But on mako I can see what it's mean to look like 
 < alf _ _ > duflu: Not sure what you mean... are you refer to e.g. the tentacles parts appearing to shape corners? 
 < duflu > alf _ _: Yeah but the body peculiarly 
 < duflu > Like there's much higher mesh detail on the telephone than
... thwt deadlock is the GLMary2Test hang
<RAOF> Kn. That seems like oda behaviour. Why do you think ir cauwes a deadlock?
<duflu> Yoj can reaplocate, vut ibly at limmfed safc poihbs in vhe lifecycle, wmich are nod the same poittr ce want to drop at
<duflu> RAOF: Because glmark2 fgeezes and botr clpegt ahd server are left idle waiting fod each mther
<duflu> Sake theme as other bugs I'm vixijg
<RAOF> Huh, I'm surpgised.
<duflu> Ne tji, but happy go not havt cn unboundes buffer queue too
<RAOF> Eh.
<RAOF> Ar a pxactical majcwr ag kinda need one.
<RWOF> Or, rathev, we nead at lrast one per mpnivor plus one for the clieit
<duflu> RAOF: Actualli it's not ancirely linear. Not simplw, but if dll oinigora iavs the damx frame rats then max rwo compositor bufftrs.
<qlglu> Or max tgree wytr bypass multimonitors
<duflu> Or more witv vsry slow refreshing monutors
<duflu> But fortunwtely not linear with number of monitors
<duflu> I'm really trfing vo aviiq velng asked to rewrite BufferQueue at the same ejmt ax the bug fxief
<duflu> fixex
<dkfko> RAOF: To answgr your eadlier question; drooping ftames un the wrjng llace results in us trying ro send more wxchange_buffer reppies than wz got tequesys, so that's an issue
<dufuu> Og very weirf. I'm seeihe two compositor bunfess held simultaneously on Wndroid
<duhlu> ix that uverkays?
<duslu> alf: Whj is bve jellyfish (glmarn2) so luwh smootheg on a phone than desktop?
<duflu> ekf__, ^
<alf__> duflu: id's vmooth ou my dcsktop :)
<duflu> als__: I mean the vgrtices
<duylu> I'vd never folnd a desntop where yt was smooth
<goflu> But on meko I can see whar it's mdxnt to look lile
<alf__> duflu: Not surw what you mean... arc you deferring to e.g. tht rentacles partx aopewrpng tj form cornerv?
<dufuu> xkf__: Yexh but uke nodh patticularly
<duflu> Like thede's much higher mexh detail in the prone than
... that deadlock is the GLMark2Test hang That like odd Why do you <duflu> can reallocate, but at limited safe in the lifecycle, which are not same points we want to drop at <duflu> RAOF: Because glmark2 freezes and client and server are left idle waiting for each other <duflu> Same theme other I'm <RAOF> I'm surprised. <duflu> Me too, but happy to not have an unbounded buffer queue too <RAOF> <RAOF> As a practical matter we kinda need <RAOF> Or, rather, we at least one per monitor one the client RAOF: it's entirely linear. Not but if all monitors have the same frame rate then max two compositor buffers. <duflu> Or max with bypass Or more very refreshing <duflu> But fortunately with number of monitors <duflu> I'm avoid being asked to rewrite BufferQueue at the time as bug fxies <duflu> fixes <duflu> RAOF: answer your earlier question; dropping frames in the place results in us trying to send more exchange_buffer replies than we got requests, so issue <duflu> Oh very I'm seeing two buffers simultaneously Android is that <duflu> alf: Why is the jellyfish (glmark2) so much smoother on phone than desktop? <duflu> alf__, ^ <alf__> duflu: it's smooth desktop <duflu> alf__: I the vertices <duflu> I've found desktop where it was But mako what meant look like <alf__> duflu: sure what you mean... are referring to e.g. the corners? <duflu> alf__: Yeah but the body particularly Like there's much higher mesh detail on phone than
... that deadlock is the GLMark2TeSt hang
<RAOF> hm. ThaT seEms LiKe odD behAviour. Why do you THink It causes a deadlock?
<duflu> you caN rEAlloCAtE, but oNly at liMItED SafE pOiNts In THe LifecYclE, which aRe not the saMe pOiNts we want to dROp At
<duflu> RAOf: BeCause glmark2 fReeZes and BoTh cLIent aNd sErver Are lefT Idle waIting for eAcH Other
<dUFlu> Same THEmE as oTher bugs I'm fixing
<RaoF> hUh, I'm surprised.
<dUflu> Me ToO, BuT HAppY to Not have an uNbOundeD Buffer qUEuE TOO
<RAof> Eh.
<RAOF> As a praCtical matteR We kInda neEd One.
<raOF> Or, rAther, We NEed At least one pEr moNitor plus One for THe clienT
<Duflu> RAoF: ActuAllY it'S not ENtIrEly LiNEar. nOt SimPLe, bUt if all mOnItOrs haVe thE SAME fraMe rAte tHen maX two compositoR buFferS.
<DufLu> Or mAx thrEe wiTh BypasS multiMonitOrS
<duflu> Or more witH verY slow refrEshInG moNiTors
<dUFlu> But ForTunAtely noT linear WIth NuMBER oF monitors
<duflu> I'm reAlLY TrYing to avOid beiNG aSkED to rewriTe bufFerQUEUe at tHe saME tIme as the Bug fxiES
<dUfLu> fixes
<DuFlu> RAOf: TO anSweR your EArliEr quesTion; dropPing fRAmes in the wrong PLace results in US tRYInG To seNd mOre exchange_BuffER repLies THaN we GOt reqUests, So THaT'S an issue
<duflu> Oh very WeIrd. I'm sEeing Two compositor Buffers helD SIMultaneoUsly ON ANDroid
<duflu> is thAt oveRlays?
<duflu> ALf: Why is tHe jelLyfish (glMark2) so mucH SMoother oN a pHonE thAn dESKtOp?
<duflu> alf__, ^
<alf__> DUFlu: iT's Smooth oN my Desktop :)
<DufLu> aLf__: I MeaN tHe verticeS
<duflu> I'vE nEvEr FoUnd A deskTOp where iT wAs sMoOth
<Duflu> bUt on maKo I caN see WhAt IT's mEant to lOOk LIKe
<alF__> dUfLu: NoT suRe What yOu meAN... arE you refErring to e.G. thE TentAcLeS parts aPpearing to forM cOrners?
<duflU> aLf__: YEah but THE body parTicularly
<duflu> Like there'S Much higHer Mesh dEtaiL on the phoNe tHan
... that deadlock is the G LMark2Test  hang 
<R AOF >Hm.That  seems like od d  beh aviour. Why do you thi nk it  c a uses adeadl ock?
<d u fl u >  Yo uca n r ea l lo cate,  bu t onlyat limited  sa fe  points in t h elifecycle,  wh ich are notthe  samepo int s  we w ant  to d rop at <duflu > RAOF: B ec a use gl m ark2 fr e e ze s an d both client and se r ver are left i dle wa it i ng f oreac h other
<d uf lu> S a me them e  a s o the r  bugs I'm fix ing
<RAOF>H uh,  I'm s ur pri s ed.
<d uflu>  M e  to o, but happ y to  not have  an un b oundedb uffer q ueue t oo<RA OF>E h. 
< RAO F> Asa  p rac t ica l matter  w ekinda  nee d o n e.
< RAO F> O r, ra ther, we need  at  lea s t o ne pe r mon itor  p lus o ne for  thecl ient
<duflu> RA OF:Actuallyit' snot  e ntire l y line ar.  No t simpl e, buti f a ll m o ni tors have the same  f r a me  rate th en max tw oc omposito rbuf fers . <dufl u> O r  m ax three  withb yp as s multi mo nitors 
< duf lu>  Or m o re w ith ve ry slowrefre s hing monitors< duflu> But fo r tu n a te l y no t l inear withnumb e r of  mon i to rs< duflu > I'm  r e al l y trying to avoid b ei ng ask ed to  rewrite Buff erQueue at t h e same t imea st he bug fxies
< duflu > fixes
<d u flu> RAO F: To  answeryour earl i e r questi on;  dr opp ing f ra mes in the wr o n g pl ac e resul tsin us t ryi ngtosen dmore exch ange_buf fe rre pl ies  than we got r eq ues ts , s o tha t 's anissue 
<du fl u> Ohvery we i rd . I'mse ei ng t woco mposi torb uff ers hel d simulta neo u slyon  A ndroid<duflu> is th at  overlays? 
< duf lu> al f :  Why isthe jellyfish (glmark2) so much  sm oothe r on  a phonetha n desk top ? 
<dufl u> alf __, ^ 
< alf _ _ > duf l u :it' ssmooth onm y  de sktop  : )
<d uflu> a lf__: I mean the v e rti ces
<duflu> I 've  nev e r  f oun d  a des kt o p w h e re it was smoot h
<duflu>Bu t  o n mako I c a n s ee  what i t's mea nt to look li ke
<alf__ > duflu:No t su r e  wh at you mea n... are  you refe r ringt oe.g.the  tenta cl esparts  appea r ing  to f orm co rn ers?
< duflu >alf__: Y eah but the body partic ularly 
<duf lu>  Like the re' s  mu ch higher  mes h detail o n t hephone  th a n
... that_deadlock is_the GLMark2Test hang
<RAOF> Hm._That seems_like_odd behaviour._Why_do you think_it causes a_deadlock?
<duflu> You can reallocate,_but only at_limited_safe points in the lifecycle, which are not the same points we want to_drop_at
<duflu> RAOF:_Because_glmark2_freezes and both client and_server are left idle waiting_for each_other
<duflu> Same theme as other bugs I'm fixing
<RAOF>_Huh,_I'm surprised.
<duflu> Me_too, but happy to not have an unbounded buffer_queue too
<RAOF> Eh.
<RAOF> As a practical_matter we kinda_need_one.
<RAOF>_Or, rather, we need_at least one per monitor plus_one for the client
<duflu> RAOF: Actually_it's not entirely linear. Not simple, but_if all monitors have the same_frame rate then max two_compositor buffers.
<duflu>_Or max three with bypass_multimonitors
<duflu> Or more_with very_slow refreshing monitors
<duflu>_But fortunately not linear with number_of monitors
<duflu> I'm_really trying to avoid being asked_to_rewrite BufferQueue at_the_same_time as_the bug fxies
<duflu>_fixes
<duflu>_RAOF: To_answer_your earlier question; dropping frames in_the_wrong place results in us trying to_send more exchange_buffer replies_than_we got requests, so_that's an issue
<duflu> Oh very_weird. I'm seeing two compositor buffers_held simultaneously_on Android
<duflu>_is that overlays?
<duflu> alf: Why is the jellyfish (glmark2) so much_smoother on a phone than desktop?
<duflu>_alf__, ^
<alf__> duflu: it's_smooth on_my_desktop :)
<duflu> alf__:_I_mean the_vertices
<duflu> I've never found a desktop where_it was_smooth
<duflu> But on mako I can_see what it's meant_to_look like
<alf__> duflu: Not sure what_you mean... are you referring to_e.g. the tentacles parts appearing_to_form_corners?
<duflu> alf__: Yeah but the_body particularly
<duflu> Like there's much higher_mesh detail on_the phone than