On Nov 12, 2007, at 6:00 PM, Jesse wrote:
Xquartz crashed on me 5 times today out of the blue as I was working and the Apple crash dialog came up for reporting the issue (I reported all instances.). If you think it would a benefit, I'd be happy to post the crash logs to the mailing list. I would like to post them somewhere in case some of you guys can identify any problems from them. It is out of my league. I'll post one in this message and someone can chime in if they'd like me to post the additional ones. The crashes are very puzzling since I have had no problems at all since the updates have been released. This also happened to my friend at work throughout the day but no other day so far...very odd.
Thread 1 Crashed:
0 Xquartz 0x0002d5f7 rlSolid + 1035
1 Xquartz 0x0002c1ac rlFill + 466
2 Xquartz 0x0002cab0 rlPolyFillRect + 340
3 Xquartz 0x0014734e damagePolyFillRect + 717
4 Xquartz 0x000217df RootlessPolyFillRect + 810
5 Xquartz 0x00080afc ProcPolyFillRectangle + 461
6 Xquartz 0x000fbbc7 XaceCatchDispatchProc + 146
7 Xquartz 0x0007c519 Dispatch + 640
8 Xquartz 0x00097b65 main + 1921
9 Xquartz 0x0000bf2c server_thread + 59
10 libSystem.B.dylib 0x91fe4075 _pthread_start + 321
11 libSystem.B.dylib 0x91fe3f32 thread_start + 34
I hate crashes in the Rootless code (anything beginning with rl or Rootless). It's the weakest point, because it's code that's specific to OS X and so we haven't had the luxury of all of the (for example) Linux coders poring over it to find bugs. :/
I've seen a couple similar crashes; no idea why this would start up again with 1.2a8.
--