Fix backgroundog ACCESS_VIOLATION crash and Unicode file path URI handling #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two unrelated issues: (1) backgroundog.exe randomly crashes with 0xC0000005 ACCESS_VIOLATION errors during Windows message processing, (2) wallpaper selection crashes when file paths contain non-ASCII characters (e.g., Chinese:
D:\壁纸\风景.jpg).Changes
Exception Handling (backgroundog crash)
AppDomain.UnhandledExceptionandTaskScheduler.UnobservedTaskExceptionglobal handlersIntPtr.Zerovalidation before native API calls (GetForegroundWindow,GetWindowThreadProcessId)GetWindowThreadProcessIdcallsFiles:
App.cs,Windows.cs,Specification.csURI Creation (Unicode paths)
Path.GetFullPath()+UriKind.Absoluteinstead ofUriKind.RelativeOrAbsoluteGetSource(string, string)overload to route through proper URI handlingFile:
Source.csAll changes are defensive additions with no breaking changes to existing functionality.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.