Skip to content
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

Crash started occuring at each new launch of DependenciesGui.exe #259

Open
bartoli opened this issue Feb 2, 2024 · 0 comments
Open

Crash started occuring at each new launch of DependenciesGui.exe #259

bartoli opened this issue Feb 2, 2024 · 0 comments

Comments

@bartoli
Copy link

bartoli commented Feb 2, 2024

Dependencies, that had been installed for months/years is today crashing at launch (latest release, windows 10 )

When launched from VS2022 debugger, the earlier exception i get is :

System.Windows.Data Error: 40 : BindingExpression path error: 'DataContext' property not found on 'object' ''String' (HashCode=-419799353)'. BindingExpression:Path=DataContext.EnableSearchFolderCustomization; DataItem='String' (HashCode=-419799353); target element is 'MenuItem' (Name='CustomizeSearchFoldersItem'); target property is 'IsEnabled' (type 'Boolean')

The call stack in project code is not very interesting:
PresentationFramework.dll!System.Windows.Markup.XamlReader.RewrapException(System.Exception e, System.Xaml.IXamlLineInfo lineInfo, System.Uri baseUri) Line 361 C#
PresentationFramework.dll!System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader xamlReader, System.Xaml.IXamlObjectWriterFactory writerFactory, bool skipJournaledProperties, object rootObject, System.Xaml.XamlObjectWriterSettings settings, System.Uri baseUri) Line 121 C#
PresentationFramework.dll!System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader xamlReader, bool skipJournaledProperties, object rootObject, System.Xaml.Permissions.XamlAccessLevel accessLevel, System.Uri baseUri) Line 38 C#
PresentationFramework.dll!System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream stream, System.Windows.Markup.ParserContext parserContext, object parent, bool closeStream) Line 763 C#
DependenciesGui.exe!Dependencies.UserSettings.UserSettings() Line 54 C#

DependenciesGui.exe!Dependencies.MainWindow.MainWindow() Line 114 C#

Inner exception stack trace is:
at MS.Internal.Text.TextInterface.Native.Util.ConvertHresultToException(Int32 hr)
at MS.Internal.Text.TextInterface.FontList.get_Item(UInt32 A_0)
at MS.Internal.FontFace.TypefaceCollection.Enumerator.get_Current()
at Dependencies.FontFamilyListItem.IsSymbolFont(FontFamily fontFamily)
at Dependencies.FontFamilyListItem..ctor(FontFamily fontFamily)
at Dependencies.UserSettings.InitializeFontFamilyList()
at Dependencies.UserSettings.OnInitialized(EventArgs e)
at System.Windows.FrameworkElement.TryFireInitialized() in System.Windows\FrameworkElement.cs:line 4204
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(XamlType xamlType, Object obj, Boolean begin)

Clearing %LOCALAPPDATA%/Dependencies does nothing, so unless 'settings' are stored somewhere else, i am not sure there are corrupted settings?

It seems like it could be related to some font not being found

Looking with iIn process monitor, the last access to a font is C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe\CascadiaCode.ttf, that returns status DELETE_PENDING

Probably an error similar to https://developercommunity.visualstudio.com/t/Visual-Studio-Editor-is-blank-without-an/1568780. I will update after reboot to see if it was indeed caused by the locked Cascadia font file (System and svchost.exe had it locked acording to process explorer)
EDIT Indeed, rebooting makes it work again

I guess there should be an exception catch somewhere to avoid this?

I can provide a crash dump if needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant