Re: Xquartz random crashes today, version 1.2a8, crash log included (now using 1.2a11)
Re: Xquartz random crashes today, version 1.2a8, crash log included (now using 1.2a11)
- Subject: Re: Xquartz random crashes today, version 1.2a8, crash log included (now using 1.2a11)
- From: Jesse <email@hidden>
- Date: Fri, 16 Nov 2007 21:35:04 -0500
Guys,
I have still been experiencing many crashes even with the latest version, 1.2a11. The X session will be stable for some period of time, some times several hours, but once the initial crash occurs, it will continue to crash over and over even after closing X and restarting many times. Each crash that occurs, produces this output at the terminal:
"X connection to /tmp/launch-xr9TuM/:0 broken (explicit kill or server shutdown)."
The /tmp location will vary, I think, but I always receive this message. Hopefully that helps point to something.
I am including some of my crash logs from today in a zip. Maybe they will offer some insights. I sometimes wonder if copy and paste operations inside the X rdesktop window initiate the crashes. What puzzles me is that fact that once the crashes start, they continue even with new X sessions.
Here is the command I am using (and used in Tiger) to start rdesktop:
rdesktop -a 16 -g 1600x1000
1.2.3.4 &
Please let me know if anything else from me would help.
Thanks,
Jesse
>> On Nov 12, 2007, at 9:15 PM, Ben Byer wrote:
>>
>>> 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.
>>
>> Ben,
>>
>> The above is totally reminiscent to me of the Rootless crashes that
>> I fixed. My guess is that it's not specific to 1.2a8 but rather to
>> whatever app that Jesse happened to be using.
>>
>> Cheers,
>> Ken
Ben Byer
CoreOS / BSD Technology Group, XDarwin maintainer
Attachment:
X.crash.logs.zip
Description: Zip archive
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden