If a Kate session includes files that are located on a Windows mapped network drive, Kate will crash if the network drive is disconnected. If the default session includes such files, Kate will crash on startup, making it impossible to open. The crash occurs if the remote computer goes offline or if you disconnect the mapped drive on the Windows machine. Reproducible: Always Steps to Reproduce: 1. Map a network drive in Windows (you can even map a shared folder on the same computer, e.g. \\127.0.0.1\C) 2. Open a file on the mapped drive in Kate 3. Press Sessions -> Save Session 4. Disconnect the mapped drive (right-click the drive in Explorer and press disconnect) Actual Results: Kate crashes. Kate will crash on startup when attempting to reopen. To workaround, you must remap the network drive. Expected Results: Kate does not crash and instead notifies user that file is no longer available. Kate version 16.07.70 built from source on Windows using Visual Studio 2015.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I rebuilt with Craft today (11/23/18). Kate version is now 18.08.3. KDE Frameworks 5.52.0 Qt 5.11.2 (built against 5.11.2) The windows windowing system Tested by mapping a network drive, opening a file on the drive, disconnecting the network, and refreshing the file in Kate, causing Kate to crash.
Can you get some backtrace?
Are you able to provide the details requested in Comment 4 if this is still an issue. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
Created attachment 149602 [details] cywgwin strace
How to get crash logs or strace (cygwin's strace not suitable for this) on windows? I confirm this problem, let's understand the reasons
I would assume one would rather use the MSVC debugger or windbg with the debug builds from binary-factory.kde.org
Hi, could you try that with a more recent version from the store? Thanks.
>could you try that with a more recent version from the store kate 23.08.2 Nothing has changed - the application crashes. As far as I could understand windbg... I managed to get something. After network drive became unreacheble. Kate freeze (windows file subsystem timeout on network drive) then crash: ``` [...] ModLoad: 00007ff9`2ab60000 00007ff9`2adfa000 C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.3570_none_60bb2a3971f3e41a\comctl32.dll ModLoad: 00007ff9`3a090000 00007ff9`3a244000 C:\WINDOWS\SYSTEM32\WindowsCodecs.dll ModLoad: 00007ff9`2d1c0000 00007ff9`2d26c000 C:\WINDOWS\SYSTEM32\TextShaping.dll (4960.1744): Stack overflow - code c00000fd (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. ntdll!RtlpDosPathNameToRelativeNtPathName+0x41: 00007ff9`3f22af91 894c2434 mov dword ptr [rsp+34h],ecx ss:0000009d`fde03ec4=00000000 ``` After crash I reload executable in windbg and go: ``` [...] ModLoad: 00007ff9`2d270000 00007ff9`2d4ef000 C:\WINDOWS\system32\dwrite.dll (4e20.3f40): Stack overflow - code c00000fd (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. ntdll!RtlProtectHeap+0x559: 00007ff9`3f21e639 e856050000 call ntdll!RtlProtectHeap+0xab4 (00007ff9`3f21eb94) ```
Created attachment 162506 [details] full windbg crash after restart with disconneted network drive
*** Bug 464010 has been marked as a duplicate of this bug. ***
*** Bug 475717 has been marked as a duplicate of this bug. ***