Process termination when working with accessibility GUI
[ab_getCurrCellBorder] [ab_resize] [ab_resize_memset] [ab_showlist] [accessibility] [accessibility.dll] [build_lsr_texts] [close_container] [ContainerInfo] [getTableLineDisplCnt] [grr3] [list_field_lsr_info] [MmxFree2] [MmxMalloc2] [MmxRealloc2] [Painter] [pore accessibility] [Report] [show_field] [web accessibility]
- Accessibility classification is incorrectSymptom Transaction SQ_REPORT_INFOSET is labeled as not accessible, even though it meets the requirements. Other terms InfoSet, report Reason and Prerequisites The label was forgotten. Solution Implement this note. ...
- Accessibility errors in Message AreaSymptom Accessibility errors occur im Message Area Other terms Accessibility, Message Area Reason and Prerequisites Accessibilty description is missing for UI elements GROUP and MULTIPANE in the Message Area Solution Please apply...
- POWL – Accessibility issue in Dynamic Dates ViewSymptom Accessibility issue in the calculated dates popup – while tabbing it navigates to the label of the dynamic data field. this should not happen Other terms powl, accessibilty issue in calculated...
Symptom
You work with the accessibility GUI, that is, you set the accessibility theme or the accessibility mode in SAP GUI.
When you display an ABAP list, the work process suddenly terminates.
The system displays a dialog box with the following message:
SAP system message:
Work process restarted; session terminatedThe system log (transaction SM21) contains the following entry:
“Signal 11 received by operating system”The ABAP runtime errors (transaction ST22) include a SYSTEM_CORE_DUMPED.
Other terms
Report Painter, report, grr3
ab_showlist close_container MmxFree2
show_field ContainerInfo list_field_lsr_info build_lsr_texts
ab_getCurrCellBorder
getTableLineDisplCnt ab_resize_memset ab_resize
MmxRealloc2 MmxMalloc2
Reason and Prerequisites
If ACC texts become larger than 256 bytes, the system internally releases the old memory area and creates a new and larger area. However, due to a program error, the system continues to use the old invalid memory. This results in various fatal memory overwrites.
Solution
Apply the relevant kernel patch.