On Mon, 10 Jul 2017 15:47:16 +0100 Mick <michaelkintz...@gmail.com> said:
> On Friday 30 Jun 2017 12:18:52 Mick wrote: > > On Thursday 29 Jun 2017 07:37:46 Carsten Haitzler wrote: > > > On Wed, 28 Jun 2017 15:06:48 +0100 Mick <michaelkintz...@gmail.com> said: > > > > built mesa with debug flags and captured another crash. Can you please > > > > scan through the backtrace below and confirm if the verdict is still the > > > > same and if anything mesa related in particular stands out which I enter > > > > in a bug report? > > > > > > sure. but keep in mind that just because e shows a bug doesnt mean other > > > compositors will. > > > > Yes, I tried had to make LO to crash KDE (plasma), but KDE's compositor > > wouldn't have any of it. No matter how much or how fast I moved the mouse > > over the menu to cause tooltips to overlap as they popped up and > > disappeared/reappeared, KDE continued to display them without freezing up. > > If I moved too fast over the tooltip generating area they just blurred a > > bit without rendering fully their content in the milliseconds they were > > given to render, before the mouse moved on to the next area. Such blurring > > would cause a freeze on evas/e. > > > > Conclusion: Plasma compositor will not cause the same crash by libdri. > > > > > > https://pastebin.com/Y6SxaKGF > > > > > > now to this... it doesn't tell me more than it did before... it's a fence > > > sync within the driver layer. it's a problem between the driver and itself > > > across process boundaries. if you want i can explain what fences are and > > > their purpose (in general) and why this would be the case and i can > > > probably narrow down where the issues are being caused in the x 2d + dri > > > driver stack... but it'll be a long explanation. i do not know the DETAILS > > > of the fence implementations down at the dri level... but i do know what > > > fences are, what they in general do and why this tells me the issue is not > > > something we can solve in efl... > > > > > > if you want the details - let me know. otherwise know that this is a bug > > > you likely have to file with the dri3/mesa/xorg 2d/radeon driver > > > people... :/ > > I thought this was a radeon driver problem. On some further testing shows > > this *also* occurs on Intel! An old Acer Incorporated [ALI] Mobile 4 Series > > Chipset (ICH9) Integrated Graphics Controller crashed in the same manner. > > This is using the i965 & intel flags in mesa, rather than > > r600/radeon/radeonsi. So it does not seem to be radeon specific. I've > > tried with mesa-17.0.6 which is when the problems seem to have started and > > with mesa-17.1.3. > > > > I've started with a report to Gentoo for now and will see what they advise. > > Would there be a setting to disable tooltip hardware acceleration in the > compositor I could select, so as to continue using e without crashing? no. it doesn't work like that. compositing is an all or nothing thing. > I tried disabling composite effects for menus/popups but it still crashes. > What category of composite effects application windows' tooltips fall under? > -- > Regards, > Mick -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
