[Bug] Fork keeps on crashing by itself with version 2.4.2.0

[db2222]

Since this version Fork constantly crashes. It can happen when I'm using the application or it is in the background.
There is no noticeable logic behind it.

It seems like a NPE bug in the background processes of Fork.

This is that I found in the Windows event log:

Anwendung: Fork.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.NullReferenceException
   bei System.Threading.Tasks.ThreadPoolTaskScheduler.LongRunningThreadWork(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Threading.ThreadHelper.ThreadStart(System.Object)

EventID = 1026

Followed by:

Name der fehlerhaften Anwendung: Fork.exe, Version: 2.4.2.0, Zeitstempel: 0x678e3804
Name des fehlerhaften Moduls: mscorlib.ni.dll, Version: 4.8.9290.0, Zeitstempel: 0x67214b29
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000f06671
ID des fehlerhaften Prozesses: 0x8708
Startzeit der fehlerhaften Anwendung: 0x01db6d841f1f2b9b
Pfad der fehlerhaften Anwendung: C:\Users\DBE\AppData\Local\Fork\app-2.4.2\Fork.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\02615d09f5932f870508f7020261bb0e\mscorlib.ni.dll
Berichtskennung: f70d413a-2862-4c09-9ba0-d7e48de8af9a
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

EventID = 1000

Every crash it is the same pattern.

Can this please be fixed urgently. Is there anything I can do besides downgrading?
As the 2.4.X versions were released so shortly after another I'm not 100% sure if a previous version also had the issue.
But if I remember correctly it should only be ever since 2.4.2.0.

Thank you!

[DanPristupov]

Is there anything I can do besides downgrading?

First, try to downgrade and confirm that this is a regression in 2.4.
Use the installer from the website.

[db2222]

Well I know definitely that it came with 2.4 as Fork never crashed before. Now it is every few minutes.

I only can't say for certain if it is 2.4.2. But I'm 90% sure.

[DanPristupov]

Try to reinstall using the installer from the website.

[RianFL]

I have the same issue. I was asked to update Fork a few days ago, and I now see a few crashes per day.
Other thing that happened recently is my IT department pushed out a 23H2 monthly and .NET runtime updates.

2025-01 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5050021)
2025-01 .NET 8.0.12 Security Update for x64 Client (KB5050525)
2025-01 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64 (KB5049624)

Faulting application name: Fork.exe, version: 2.4.2.0, time stamp: 0x678e3804
Faulting module name: clr.dll, version: 4.8.9290.0, time stamp: 0x67214bca
Exception code: 0xc0000005
Fault offset: 0x00000000000638cf
Faulting process id: 0x0x2100
Faulting application start time: 0x0x1DB6D6C58D5023A
Faulting application path: C:\Users<snip>\AppData\Local\Fork\app-2.4.2\Fork.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 7743277e-e578-48a3-b53a-a8818985fa97
Faulting package full name:
Faulting package-relative application ID:

Application: Fork.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFBA66A38CF (00007FFBA6640000) with exit code 80131506.

[tupjohn]

I am experiencing the same behavior for the same reasons as above.

To add some color to the conversation, my Fork seems to crash soon after moving to an older commit and interacting with the Changes in the lower window. Expanding the change, collapsing, etc. After about 5 minutes from doing that the application will crash.

This happened several times yesterday and after NOT doing any of that for well over an hour with the application stable I tried again the above steps. Sure enough, 5 minutes (or so) later it crashed.

I have reinstalled the application without uninstalling, I have uninstalled and reinstalled and I have restarted my PC. Each time the application updates to the latest.

[DanPristupov]

@tupjohn

To add some color to the conversation, my Fork seems to crash soon after moving to an older commit and interacting with the Changes in the lower window. Expanding the change, collapsing, etc. After about 5 minutes from doing that the application will crash.

Can you take an attention to this, please? Does this commit contain files with emojis/unicode characters? Try to select this commit multiple times, does it make Fork crash sooner?

[tupjohn]

@tupjohn

To add some color to the conversation, my Fork seems to crash soon after moving to an older commit and interacting with the Changes in the lower window. Expanding the change, collapsing, etc. After about 5 minutes from doing that the application will crash.

Can you take an attention to this, please? Does this commit contain files with emojis/unicode characters? Try to select this commit multiple times, does it make Fork crash sooner?

Well, this time it stayed up for 10 minutes. There are no emojis or special characters in that commit. It crashed at the point where I had to move the window, which was in my way. So I don't know if it was the move or the commit at this point. I will continue to monitor for similarities in actions.

Event view has this stack trace same as above:

Application: Fork.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IndexOutOfRangeException
   at System.Threading.ThreadPoolWorkQueue+WorkStealingQueue.LocalPop(System.Threading.IThreadPoolWorkItem ByRef)
   at System.Threading.ThreadPoolWorkQueue.Dequeue(System.Threading.ThreadPoolWorkQueueThreadLocals, System.Threading.IThreadPoolWorkItem ByRef, Boolean ByRef)
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

[DanPristupov]

I made a debug build where I commented out some code.

Extract the archive somewhere and run fork.exe.

https://cdn.fork.dev/prerelease/ForkWin-2.4.10.zip

Can you try if it crashes?

[DanPristupov]

Do you use context search (Ctrl+F)? It's possible it's related.

[RianFL]

I've also been using ctrl+f a lot lately for looking up commit hashes. Will try the debug build tomorrow.

…

________________________________ From: Dan ***@***.***> Sent: Thursday, January 23, 2025 8:50:12 PM To: fork-dev/TrackerWin ***@***.***> Cc: Maxime M. ***@***.***>; Comment ***@***.***> Subject: Re: [fork-dev/TrackerWin] [Bug] Fork keeps on crashing by itself with version 2.4.2.0 (Issue #2413) Do you use context search (Ctrl+F)? It's possible it's related. — Reply to this email directly, view it on GitHub<#2413 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA26LHCWLULPPIB2DB3ZMLT2MFBXJAVCNFSM6AAAAABVXCXCL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJQHA4DCOJRHE>. You are receiving this because you commented.Message ID: ***@***.***>

[tupjohn]

Do you use context search (Ctrl+F)? It's possible it's related.

Yes, that is something I have been doing...maybe before every crash? I haven't tracked that exactly.

update since I am writing this other comment: Debug build has been stable for 30 minutes

[db2222]

I explicitly tried it on another private machine with 2.4.2.0. The only thing that I did is use Ctrl+F to search in different repos. Then I did other things on the machine (Fork in the background). Fork then has crashed. The same errors in the Windows log. I strongly assume that you are on the right track for the origin of the issue.

[DanPristupov]

We are releasing the hotfix!

[DanPristupov]

The 2.4.3 hotfix is out! 🚀