-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Bug: 映射网络驱动器,意外断开后崩溃且Files重启卡死 #16328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the feedback. If you can open Files when you didn't open that Ubuntu folder, can you take a look at the log location from Settings > About > Open log location? |
我无法以任何方式打开Files,它会在加载界面崩溃。另外,在Windows原生的explorer中,如果我尝试去左键/右键点击这个网络驱动器图标,explorer也会崩溃,不过explorer不会在启动时崩溃。 |
Can you take a look at Windows Event Viewer (Windows Logs > Application)? |
这是我的事件记录: 事件的信息:
其中一个事件的 Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" Guid="{c631c3dc-c676-59e4-2db3-5c0af00f9675}" />
<EventID>1002</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-10-09T17:46:51.3174699Z" />
<EventRecordID>43096</EventRecordID>
<Correlation />
<Execution ProcessID="32388" ThreadID="35580" />
<Channel>Application</Channel>
<Computer>WORKER-4080S</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AppName">Files.exe</Data>
<Data Name="AppVersion">1.0.0.0</Data>
<Data Name="ProcessId">0x86e4</Data>
<Data Name="StartTime">0x1db1a73337369dc</Data>
<Data Name="TerminationTime">46</Data>
<Data Name="ExeFileName">C:\Program Files\WindowsApps\Files_3.7.7.0_x64__1y0xx7n9077q4\Files.App\Files.exe</Data>
<Data Name="ReportId">5a774ed8-b225-485e-82f3-526fa05170b3</Data>
<Data Name="PackageFullName">Files_3.7.7.0_x64__1y0xx7n9077q4</Data>
<Data Name="PackageRelativeAppId">App</Data>
<Data Name="HangType">Unknown</Data>
</EventData>
</Event> 我尝试在对应目录寻找是否有Files生成的日志,但是找不到了。(因为只有卸载了Files后我的explorer才能正常使用,所以我卸载了Files) |
这是原生的explorer在执行相似操作时崩溃产生的日志:
事件 Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-10-10T01:54:11.1262024Z" />
<EventRecordID>43202</EventRecordID>
<Correlation />
<Execution ProcessID="61324" ThreadID="37284" />
<Channel>Application</Channel>
<Computer>WORKER-4080S</Computer>
<Security UserID="S-1-5-21-2506697481-2255580763-1697903707-1002" />
</System>
<EventData>
<Data Name="AppName">explorer.exe</Data>
<Data Name="AppVersion">10.0.22621.4291</Data>
<Data Name="AppTimeStamp">47ba1b55</Data>
<Data Name="ModuleName">ntdll.dll</Data>
<Data Name="ModuleVersion">10.0.22621.4291</Data>
<Data Name="ModuleTimeStamp">c2dc6aa6</Data>
<Data Name="ExceptionCode">c0000374</Data>
<Data Name="FaultingOffset">000000000010cae9</Data>
<Data Name="ProcessId">0xc9b4</Data>
<Data Name="ProcessCreationTime">0x1db1a74f4c6a6aa</Data>
<Data Name="AppPath">C:\Windows\explorer.exe</Data>
<Data Name="ModulePath">C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data Name="IntegratorReportId">6274c86d-db91-4556-941e-a46c4f3e3463</Data>
<Data Name="PackageFullName">
</Data>
<Data Name="PackageRelativeAppId">
</Data>
</EventData>
</Event> |
This may be the same issue as #16377 as the same ntdll.dll is reported. |
Is this still an issue in the preview version? https://files.community/download/preview |
@LifeCheckpoint Can you answer the above question |
Description
我在VMware中通过映射网络驱动器的方式将一个Ubuntu的虚拟硬盘映射到Windows中,然后在Files里打开了它。
随后,因为对Ubuntu目录的权限操作错误(将Ubuntu根目录误设为最低权限),虚拟机中的Ubuntu意外与外界断连。
此时我尝试在Files中打开从Ubuntu映射过来的文件夹,Files就卡死然后崩溃。
最后,无论我如何尝试打开Files,Files都会卡在加载界面显示转圈动画,窗口也无响应,随后崩溃。
Steps To Reproduce
Requirements
修复Files对于网络驱动器意外断开的处理机制,防止卡死问题发生
Files Version
(Release) 3.7
Windows Version
win11 23H2 22635.4291
User ID
No response
Log File
由于Files损坏且explorer无法打开,只能卸载Files后尝试搜索/恢复log文件,但是最终在对应文件夹(AppData)没能找到它
The text was updated successfully, but these errors were encountered: