http://bugs.freedesktop.org/show_bug.cgi?id=20647
--- Comment #12 from Alex Deucher <ag...@yahoo.com> 2009-03-16 10:45:33 PST --- (In reply to comment #11) > I've been using 2 without a problem. > ok. > However, should a buggy app be able to make the Xserver go nuts like that? > i.e. consume 100% cpu even when the program is forcably killed and the Xserver > not be able to be forcably killed? > If the app uses GL, the 3D driver converts GL to hardware commands which are fed to the chip. Something about that command stream (perhaps in combination with the 2D command stream from the 2D driver loaded by the xserver) is causing the GPU to hang. Once that happens generally, you're done. The 2D driver is generally stuck looping in an ioctl waiting for idle, etc. which is what causes the CPU to spike. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
