Changes between Initial Version and Version 1 of Ticket #13191, comment 37


Ignore:
Timestamp:
Jul 30, 2018, 12:00:17 AM (6 years ago)
Author:
cocobean

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13191, comment 37

    initial v1  
    1 @waddlesplash - Not useless when one crosses the finish line with it. I am specifically proving "Selecting Flurry screensaver does not crash ScreenSaver preflet" by using an alternative and 'when' the issue started occurring. After two years of this post, did anyone else specify that as well (or about other issues I mentioned in detail)? Not trying to troll the issue or ticket here or be a jerk about it...
     1@waddlesplash - Not useless when one crosses the finish line with it. I am specifically proving "Selecting Flurry screensaver does not crash ScreenSaver preflet" by using an alternative and 'when' the issue started occurring.
    22
    3 @kallisti5 - You fixed the original code issue I had with mesa-swpipe. I backported your patches for the Mesa 17.1 build review as well. Since I got things where the flurry screensaver didn't crash during operation and open/closes properly within the Screensaver preflet (and I can mouse control the GLTeapot) - I'll isolate any remaining mesa-swpipe driver code issues on my end. Thank you.
     3@kallisti5 - Applied patches and built Mesa 18.2 (git). The issue I found was the BeOS BScreensaver create/exit handling code in Flurry.h. Most of the GL apps/code I've ran successfully without any crashes or screen open/exit issues didn't have BeOS handling code and seem to work fine with mesa-swpipe. All the other GL apps I tested properly exit and kill app threads without the BeOS-specific code... I'll review porting Flurry from that perspective.
     4
     5Tested with Mesa mesa-swpipe 17.1.10, 18.1.5, & 18.2 (git)
     6
     7NOTE: Since I got things where the flurry screensaver didn't crash during operation and open/closes properly within the Screensaver preflet (and I can mouse control the GLTeapot) - I'll isolate any remaining mesa-swpipe driver issues on my end. Thanks.