[QGIS-trac] Re: [Quantum GIS] #1806: QGIS crashes/has graphical "glitch" on Windows Vista 64bit

[Quantum GIS]

#1806: QGIS crashes/has graphical "glitch" on Windows Vista 64bit
--------------------------------------------------------------+-------------
        Reporter:  kumba                                      |         Owner:  nobody       
            Type:  bug                                        |        Status:  new          
        Priority:  critical: causes crash or data corruption  |     Milestone:  Version 1.2.0
       Component:  MapCanvas                                  |       Version:  HEAD         
      Resolution:                                             |      Keywords:               
Platform_version:                                             |      Platform:  Windows      
        Must_fix:  Yes                                        |   Status_info:  0            
--------------------------------------------------------------+-------------
Changes (by kumba):

  * priority:  major: does not work as expected => critical: causes crash
               or data corruption
  * summary:  QGIS crashes WAY too much on Windows platforms => QGIS
              crashes/has graphical "glitch" on Windows Vista
              64bit

Comment:

 Just ran into this again.  Interestingly enough, it did not crash this
 time.  I played around in what was left of the interface, and noted a few
 things:

 - Layer window still functions, can be moved around and even closed.
 - Print Screen button does not function, and will not copy a screenshot
 into the clipboard.
 - Main map window is completely inoperative when this occurs,
 minimize/maximize operations do nothing, and the taskbar is muddled until
 you switch away from the application.  If you switch to another app, then
 attempt to switch back to QGIS, nothing happens.  The taskbar button is
 depressed, but no window updates happen, and graphical drawing artifacts
 can appear depending on what else you do in the window, however, the map
 canvas area is able to be "clicked through" to the underlying windows
 application, which will switch to it at this point.

 I was able to trigger this while zoomed into road-level data of Frederick
 County, MD, using Tigerline datasets.  The other visible layers were
 surrounding counties in MD, WV, and VA (County 2000, Designated Places
 2000, and Water polygons), and some custom layers I've created.

 The actual trigger was using the select/lasso tool, and I was in the
 middle of selecting a line element, with rendering on.  It was when I
 released the mouse button, triggering the rendering operation to start to
 display the color of the selected line, that it occurred.  The dotted gray
 box indicating my selection box remained partially on the screen at this
 point, but everything else was blanked then.

 I'm going to up this back to critical -- I haven't seen data corruption
 happen at this point, but I can trigger this pretty consistently it seems.
 It is random, but so far consistent.  Should I try the 1.2 nightlies?
 (Assuming 1.2 is the nightly stuff you've referenced)

-- 
Ticket URL: <https://trac.osgeo.org/qgis/ticket/1806#comment:6>
Quantum GIS <http://qgis.org>
Quantum GIS is an Open Source GIS viewer/editor supporting OGR, PostGIS, and GRASS formats