Re: [chandler-dev] Possible workaround for drag-and-crash bug on Mac OS X

On 17 Dec, 2008, at 18:48, Graham Perrin wrote:

>
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=12464>
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=12463>
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=12447>
>
> My strong sense, after creating 12464, is that the two most recent are
> duplicates of 12447. Thanks to
> Grant Baillie <https://bugzilla.osafoundation.org/show_bug.cgi?id=12463#c1 
> >
> for planting the suggestion.
>
> If anyone with Mac OS X crash report intuition can consider the crash
> reports (alone) attached to 12464 and 12463, and agree that they are  
> indeed
> duplicates of 12447, then I have a possible workaround.

Hi, Graham

Looking at the stack traces (although I don't see one in Bug 12447), I  
think these bugs all have the same cause as:

<https://bugzilla.osafoundation.org/show_bug.cgi?id=11696>

In all cases, the top of the stack looks like:

Thread 0 Crashed:
0   com.apple.QD                  	0x95c913cd _SetDstBits32BGRA + 8
1   com.apple.QD                  	0x95c84c95 DevRgn + 301
2   com.apple.QD                  	0x95c84aa5 StdRgn + 671
3   com.apple.QD                  	0x95c84800 CallRgn + 50
4   com.apple.HIToolbox           	0x9621b46e MyDrawingProc + 101
5   com.apple.QD                  	0x95cb2569 CommonDeviceLoop + 918
6   com.apple.HIToolbox           	0x9621b514 InvertMyRegion + 164
7   com.apple.HIToolbox           	0x9621b806 HideDragHilite + 132

with the frames above that depending on what specific drag is occurring.

Reading through the comments in this last bug, we incorporated an  
attempt at a fix by a wx developer, but apparently it didn't work.

--Grant

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev