That's not what meant but it's a good idea. What I thought was that some kind of plug in or scripting was sending something wrong to X and that messed it up. While X should be able to handle bad input, I was thinking that flash or javascripting was the culprit, sending the wrong type someplace so that X gets terminated. After all, none of the other applications I run manage to crash X. At the same time, few of the applications I run do as many things with as many different types of data as my browser does.
Let me know how core two works out. I've heard that it's come a long way in the last year or so. On Wednesday 13 October 2004 16:28, michael dolan wrote: > It makes perfect sense that it would be some corruption in X, rather > than a browser. > > Michael
