| Summary: | Dump which temporary freezes Writer with sal3.dll (no crash) | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Timur <timur> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INSUFFICIENTDATA | ||
| Severity: | normal | CC: | michael.stahl |
| Priority: | medium | Keywords: | haveBacktrace |
| Version: | 5.2.6.2 release | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=99909 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: |
Dump with procdump
Dump with procdump sal3!FileHandle_Impl |
||
Created attachment 135348 [details]
Dump with procdump sal3!FileHandle_Impl
Another dump with LO 5.2.7., somewhat different.
STACK_COMMAND: ~0s; .ecxr ; kb
FOLLOWUP_IP:
sal3!FileHandle_Impl::readAt+6c [c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file.cxx @ 307]
6c0c807c 85c0 test eax,eax
FAULTING_SOURCE_LINE: c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file.cxx
FAULTING_SOURCE_FILE: c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file.cxx
FAULTING_SOURCE_LINE_NUMBER: 307
FAULTING_SOURCE_CODE:
No source found for 'c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file.cxx'
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: sal3!FileHandle_Impl::readAt+6c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sal3
IMAGE_NAME: sal3.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 59019294
FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_sal3.dll!FileHandle_Impl::readAt
BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_sal3!FileHandle_Impl::readAt+6c
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:status_breakpoint_80000003_sal3.dll!filehandle_impl::readat
FAILURE_ID_HASH: {4131105f-6718-ae5e-3814-3f03b6a72ad5}
Followup: MachineOwner
Hi Michael, sorry to bother you, but in Bug 99909 you wrote to re-open if I can reproduce in 5.1 or later. So I open a new bug. And those 2 dumps are from LO 5.2.7. It's not just dump, it freezes Writer for a while so it's inconvenient. Another example of dump which freezes Writer 5.2.7.2 for a while with:
STACK_COMMAND: ~0s; .ecxr ; kb
FOLLOWUP_IP:
sal3!osl_acquireMutex+c [c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\mutex.c @ 72]
6ceda6dc b001 mov al,1
FAULTING_SOURCE_LINE: c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\mutex.c
FAULTING_SOURCE_FILE: c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\mutex.c
FAULTING_SOURCE_LINE_NUMBER: 72
FAULTING_SOURCE_CODE:
No source found for 'c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\mutex.c'
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: sal3!osl_acquireMutex+c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sal3
IMAGE_NAME: sal3.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 59019294
FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_sal3.dll!osl_acquireMutex
BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_sal3!osl_acquireMutex+c
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:status_breakpoint_80000003_sal3.dll!osl_acquiremutex
FAILURE_ID_HASH: {44d0c9e8-bfe3-c69c-c84b-92f2e78a39da}
|
Created attachment 133527 [details] Dump with procdump While using Writer 5.2.6.2, full profile with extensions, I got procdump. Writer didn't crash. Reason I'm using procdump is because I got crash on that file. I don't know when it happened so cannot reproduce but I get a crash rather frequently, mostly on paste or undo, so I'm trying to find the cause. STACK_COMMAND: ~0s; .ecxr ; kb FOLLOWUP_IP: sal3!GetCaseCorrectPathNameEx+1df [c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file_url.cxx @ 422] 5beac45f 89858cfdffff mov dword ptr [ebp-274h],eax FAULTING_SOURCE_LINE: c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file_url.cxx FAULTING_SOURCE_FILE: c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file_url.cxx FAULTING_SOURCE_LINE_NUMBER: 422 FAULTING_SOURCE_CODE: No source found for 'c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file_url.cxx' SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: sal3!GetCaseCorrectPathNameEx+1df FOLLOWUP_NAME: MachineOwner MODULE_NAME: sal3 IMAGE_NAME: sal3.dll DEBUG_FLR_IMAGE_TIMESTAMP: 58b70cfa FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_sal3.dll!GetCaseCorrectPathNameEx BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_sal3!GetCaseCorrectPathNameEx+1df ANALYSIS_SOURCE: UM FAILURE_ID_HASH_STRING: um:status_breakpoint_80000003_sal3.dll!getcasecorrectpathnameex FAILURE_ID_HASH: {bc3a0d76-47af-5344-c66d-3066fc8cdb45} Followup: MachineOwner ---------