Apache OpenOffice (AOO) Bugzilla – Issue 87833
[aqua11y] Crash when deleting a note
Last modified: 2013-08-07 14:43:03 UTC
In CWS aqua11y01: - VoiceOver on - new text document - Insert the dummy text ("dt"+F3) - set the cursor in the middle of the text at the begining of a line - Press 2 times Return -> the document looks now like: Paragraph1 Paragraph2 (empty) Paragraph3 (cursor set at the begining of this paragraph) - Insert a note (Alt+Command+N) - type something in the note (not sure this is mandatory) - leave the note (Esc) - Press Backspace 2 times (deletes the empty paragraph and tries to delete the previous paragraph mark) -> Crash Infos: - this does not happen when VoiceOver is off - this does not happen on other comparable systemes (Solaris Nevada, Gnome with atk-bridge) when A11y is on - this seems not to happen when deleting only empty paragraphs or only paragraphs with text or without notes.
Keywords: aqua,accessibility,crash,oooqa
@fne: of course I'd like to have this for Beta but time is short and I don't know if we can live with this somehow pretty complex crash scenario. Comments?
>>type something in the note (not sure this is mandatory) yes, it is, ESC on an empty note just deletes the note >>Press Backspace 2 times (deletes the empty paragraph and tries to delete the >>previous paragraph mark) After ESC, the cursor is behind the note, so BACKSPACE should delete the note first This crash could have been fixed by mba in notes3, not sure though if this could be a scenario for this bug, but it sounds like a timing thing as it does not happen on other platforms @mba: could Issue 87673 have fixed this or am I wrong here? @fne: I guess you could just merge notes3 into your cws and see if that fixes the crash. It would be also nice to know where exactly it crashes
This crash happens on Leopard but *not* on Tiger. So I assume this is a VoiceOver related problem. I will contact Apple to clarify.
Actually I do not have to insert a note to get this crash - for me deleting the paragraphs just created is enough to trigger it. Here is the backtrace of this crash (VCL build with debug): Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0xc0000023 0x968096e8 in objc_msgSend () (gdb) bt #0 0x968096e8 in objc_msgSend () #1 0x934c1296 in CFGetTypeID () #2 0x958192de in getSerializeMethodForType () #3 0x958191b6 in AXSerializeCFType () #4 0x958358cf in serializeWrapper () #5 0x95835c45 in _AXXMIGCopyAttributeNames () #6 0x9583cdc8 in _XCopyAttributeNames () #7 0x95806a28 in mshMIGPerform () #8 0x934bf921 in CFRunLoopRunSpecific () #9 0x934bfd18 in CFRunLoopRunInMode () #10 0x917326a0 in RunCurrentEventLoopInMode () #11 0x917324b9 in ReceiveNextEventCommon () #12 0x9173232d in BlockUntilNextEventMatchingListInMode () #13 0x908ae7d9 in _DPSNextEvent () #14 0x908ae08e in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] () #15 0x00c35d85 in AquaSalInstance::Yield (this=0x3621910, bWait=true, bHandleAllCurrentEvents=false) at /Volumes/Data/aqua11y01/DEV300/vcl/aqua/source/app/salinst.cxx:650 #16 0x0092d851 in Application::Yield (bAllEvents=false) at /Volumes/Data/aqua11y01/DEV300/vcl/source/app/svapp.cxx:557 #17 0x0092d8a8 in Application::Execute () at /Volumes/Data/aqua11y01/DEV300/vcl/source/app/svapp.cxx:516 #18 0x00013110 in desktop::Desktop::Main () #19 0x00937779 in ImplSVMain () at /Volumes/Data/aqua11y01/DEV300/vcl/source/app/svmain.cxx:259 #20 0x00c34932 in AquaSalInstance::handleAppDefinedEvent (pEvent=0x3641cb0) at /Volumes/Data/aqua11y01/DEV300/vcl/aqua/source/app/salinst.cxx:544 #21 0x00c38804 in -[VCL_NSApplication sendEvent:] (self=0x361a9d0, _cmd=0x9680f518, pEvent=0x3641cb0) at vclnsapp.mm:64 #22 0x908a70f9 in -[NSApplication run] () #23 0x9087430a in NSApplicationMain () #24 0x00c339fa in ImplSVMainHook (pbInit=0xbffff9af "") at /Volumes/Data/aqua11y01/DEV300/vcl/aqua/source/app/salinst.cxx:205 #25 0x009378f7 in SVMain () at /Volumes/Data/aqua11y01/DEV300/vcl/source/app/svmain.cxx:297 #26 0x00002773 in main () Maybe the stack gives somebody an idea what might have happened shortly before OOo crashed ..
Could someone verify if this issue still happens in the most recent build?
Problem still present in DEV300_m9. Seems to be a problem in the accessibility bridge and/or VoiceOver anyway. I will test m10 as I've built it.
Same with m10.
Crashed even without creating a note. Crashed when paragraph was deleted. Caret position of new focused paragraph was -1, which is invalid value for VO. We return nil now instead of invalid SelectedTextRange.
Re-assigned to QA for verification.
Verified in CWS aqua11y02
I test this Issue in version m28 (OOo-Dev_DEV300_m28_MacOSXIntel_AQUA_install_en-US.dmg) on MAC OS X 10.5.4. OOo doesn't crash in this Version, also I activate VoiceOver! This Issue can therefore are closed.
Thanks to torwart Closing issue