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

Fork crashes while starting #2398

Open
XaviLC opened this issue Dec 31, 2024 · 22 comments
Open

Fork crashes while starting #2398

XaviLC opened this issue Dec 31, 2024 · 22 comments

Comments

@XaviLC
Copy link

XaviLC commented Dec 31, 2024

Hello,

I am experiencing a start crashes with Fork 2.3.1.0. Looking at windows event log I can see this error

Faulting application name: Fork.exe, version: 2.3.1.0, time stamp: 0x6749f5fd
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000776d635a
Faulting process id: 0x1ecc
Faulting application start time: 0x01db5b5551c68bbf
Faulting application path: C:\Users\nxf59937\AppData\Local\Fork\app-2.3.1\Fork.exe
Faulting module path: unknown
Report Id: ec6e791a-060a-4f39-a9f9-b598a1c444f3
Faulting package full name: 
Faulting package-relative application ID: 

I tried to uninstall and reinstall and it did work till I rebooted my laptop. How can I provide more log on this?

@DanPristupov
Copy link
Contributor

There must be another entry in the even log with the call stack. Can you send it, please?

@XaviLC
Copy link
Author

XaviLC commented Dec 31, 2024

There must be another entry in the even log with the call stack. Can you send it, please?

mmm I cannot find it. Do you mean this one maybe?
image

@DanPristupov
Copy link
Contributor

An application crash consists of two entries in Event Handler. The first one is the header, the second one is the call stack. I need the second one.

Do you mean this one maybe?

Right the next one.

@XaviLC
Copy link
Author

XaviLC commented Dec 31, 2024

An application crash consists of two entries in Event Handler. The first one is the header, the second one is the call stack. I need the second one.

Do you mean this one maybe?

Right the next one.

This one ?
image

if not please guide me a bit I don't know how to get that call stack

@DanPristupov
Copy link
Contributor

The Source must be .NET Runtime. Here is the example:
Screenshot 2024-12-31 at 10 09 40

Weird, I don't see one on your screenshot.

When did it start happening? Did you install any system updates?

@XaviLC
Copy link
Author

XaviLC commented Dec 31, 2024

The Source must be .NET Runtime. Here is the example: Screenshot 2024-12-31 at 10 09 40

Weird, I don't see one on your screenshot.

When did it start happening? Did you install any system updates?

Indeed, I cannot find it... Yes there were some automatic updated applied in the laptop I do use. I noticed yesterday, after coming back from holidays and switching on the machine. I hadn't experienced it before holidays (2 weeks ago from now)

@DanPristupov
Copy link
Contributor

Can you check, may be some old version works?

https://cdn.fork.dev/win/Fork-2.1.exe or even https://cdn.fork.dev/win/Fork-1.97.exe?

@XaviLC
Copy link
Author

XaviLC commented Dec 31, 2024

I have noticed another thing, if I reinstall Fork it does start and work but as soon as I close it, it will start crashing on starting up... Also I have looked this old issue but my VScode is not a preview but an official one (I believe)
image

@XaviLC
Copy link
Author

XaviLC commented Dec 31, 2024

Can you check, may be some old version works?

https://cdn.fork.dev/win/Fork-2.1.exe or even https://cdn.fork.dev/win/Fork-1.97.exe?

I have tried 2.1 and I see same behaviour as soon as I close it doesn't start up

@DanPristupov
Copy link
Contributor

if I reinstall Fork it does start and work but as soon as I close it, it will start crashing on starting up...

Interesting.

  1. Can you send %localappdata%\fork\logs\fork.log to [email protected], please?
  2. Can you check if %localappdata%\fork\settings.json exists and is not corrupted?

@XaviLC
Copy link
Author

XaviLC commented Dec 31, 2024

if I reinstall Fork it does start and work but as soon as I close it, it will start crashing on starting up...

Interesting.

1. Can you send `%localappdata%\fork\logs\fork.log` to [[email protected]](mailto:[email protected]), please?

2. Can you check if `%localappdata%\fork\settings.json` exists and is not corrupted?

I have sent the email, I don't see things wrong on the settings.json but I cannot asses whether the file is corrupted though...

@DanPristupov
Copy link
Contributor

I don't see any problem in the log.
Can you try to remove %localappdata%\fork\settings.json and start Fork again. Does it start?

@XaviLC
Copy link
Author

XaviLC commented Dec 31, 2024

I don't see any problem in the log. Can you try to remove %localappdata%\fork\settings.json and start Fork again. Does it start?

I renamed the file and Fork doesn't start at all

@XaviLC
Copy link
Author

XaviLC commented Jan 2, 2025

@DanPristupov is there another way that I can provide more info or logs?

@DanPristupov
Copy link
Contributor

is there another way that I can provide more info or logs?

Looks like the application crashes before the start so, logs will not help. Try to observe what leads to crash.

if I reinstall Fork it does start and work but as soon as I close it, it will start crashing on starting up...

Try to reinstall (this way it will work), run and immediately close it without opening any repo. Does it work after that?

@XaviLC
Copy link
Author

XaviLC commented Jan 3, 2025

is there another way that I can provide more info or logs?

Looks like the application crashes before the start so, logs will not help. Try to observe what leads to crash.

Ok I understand

if I reinstall Fork it does start and work but as soon as I close it, it will start crashing on starting up...

Try to reinstall (this way it will work), run and immediately close it without opening any repo. Does it work after that?

I have tried and no it doesn't work

@DanPristupov
Copy link
Contributor

Try to reinstall (this way it will work), run and immediately close it without opening any repo. Does it work after that?

I have tried and no it doesn't work

Thinking logically, it means that either Fork leaves some state on your disk (but you already tried to delete the config) or something is your system tracks it and doesn't not allow to run the second time.

  1. Try to remove %localappdata%\Fork to something else (say '%localappdata%\Fork2'). Does it start after that?
  2. Do you have an antivirus?

@XaviLC
Copy link
Author

XaviLC commented Jan 6, 2025

1. Try to remove `%localappdata%\Fork` to something else (say '%localappdata%\Fork2'). Does it start after that?

If I rename it to Fork1 it doesn't start it, also all icons on desktop are gone (obviously)

2. Do you have an antivirus?

Yes I do have it,this symantec stuff not fully managed by me, but I checked its logs too and I don't see any fork process being blocked....

@XaviLC
Copy link
Author

XaviLC commented Jan 7, 2025

I have managed to get more log when starting Fork for first time. Basically I installed Fork again, save the log, run Fork with my repo and save Fork log again. I have enacted some of the path and settings...
This log is attached fork - firstChecking.log
I see some weird errors

File name: 'C:\Users\nn\AppData\Local\Fork\packages\.betaId'
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
   at System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost)
   at Squirrel.UpdateManager.CheckForUpdateImpl.getOrCreateStagedUserId()

and

File name: 'C:\Users\nn\AppData\Local\Fork\packages\Fork-2.3.0-delta.nupkg'
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at NuGet.ZipPackage.<>c__DisplayClass9_0.<.ctor>b__0()
   at NuGet.ZipPackage.EnsureManifest()
   at Squirrel.ReleaseEntry.GetReleaseNotes(String packageDirectory)
   at Squirrel.UpdateInfo.<FetchReleaseNotes>b__19_0(ReleaseEntry x)

Does this help @DanPristupov

@DanPristupov
Copy link
Contributor

Interesting. I think this is just a normal update process from 2.3.0 to 2.3.1. However we can check if it breaks something.

  1. Try to turn off internet and install Fork without the network. Can you run the application second time with no internet?
  2. Try to run %localappdata%\fork\app-2.3\Fork.exe and %localappdata%\fork\app-2.3.1\Fork.exe directly.

@XaviLC
Copy link
Author

XaviLC commented Jan 7, 2025

1. Try to turn off internet and install Fork without the network. Can you run the application second time with no internet?

Nope, unfortunately not

2. Try to run `%localappdata%\fork\app-2.3\Fork.exe` and `%localappdata%\fork\app-2.3.1\Fork.exe` directly.

I tried but still same behaviour

@XaviLC
Copy link
Author

XaviLC commented Jan 8, 2025

I have noticed that there are dmp files of the Fork crash in my system, I have parsed them with WindDbg

Loading Dump File [C:\Users\nn\AppData\Local\CrashDumps\Fork.exe.28976.dmp]
User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 19045 MP (20 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Wed Jan  8 08:06:05.000 2025 (UTC + 1:00)
System Uptime: 0 days 23:02:02.191
Process Uptime: 0 days 0:00:02.000
.........
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr
(7130.569c): Access violation - code c0000005 (first/second chance not available)

+------------------------------------------------------------------------+
| This target supports Hardware-enforced Stack Protection. A HW based    |
| "Shadow Stack" may be available to assist in debugging and analysis.   |
| See aka.ms/userhsp for more info.                                      |
|                                                                        |
| dps @ssp                                                               |
|                                                                        |
+------------------------------------------------------------------------+

For analysis of this file, run !analyze -v
00000000`63d36500 ??              ???
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 250

    Key  : Analysis.Elapsed.mSec
    Value: 244

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 11

    Key  : Analysis.Init.CPU.mSec
    Value: 921

    Key  : Analysis.Init.Elapsed.mSec
    Value: 20774

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 68

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Failure.Bucket
    Value: SOFTWARE_NX_FAULT_c0000005_unknown.dll!noop

    Key  : Failure.Hash
    Value: {831d0811-1ea2-ade7-1bca-bc3a623ec739}

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 82922

    Key  : Timeline.Process.Start.DeltaSec
    Value: 2

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 2.3.1.0


FILE_IN_CAB:  Fork.exe.28976.dmp

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=000001ee4fddee60 rcx=00000000000000c4
rdx=ffffffffffffffff rsi=000001ee4fddee90 rdi=000001ee4fdd6c40
rip=0000000063d36500 rsp=000000c4f0fff568 rbp=000000c4f0fff5f0
 r8=000001ee4fddee90  r9=0000000000000000 r10=00000000000000c4
r11=00007fff0d744d42 r12=ffffffffffffffff r13=000000c4f0b42000
r14=000000007ffe0300 r15=0000000000800000
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010204
00000000`63d36500 ??              ???
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000063d36500
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000063d36500
Attempt to execute non-executable address 0000000063d36500

PROCESS_NAME:  Fork.exe

EXECUTE_ADDRESS: 63d36500

FAILED_INSTRUCTION_ADDRESS: 
+0
00000000`63d36500 ??              ???

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000063d36500

IP_ON_HEAP:  0000000063d36500
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

IP_IN_FREE_BLOCK: 63d36500

STACK_TEXT:  
000000c4`f0fff568 00007fff`0d744d42     : 000001ee`4fddee60 000001ee`4fdd6c40 000001ee`4fdd6c40 00000000`00000000 : 0x63d36500
000000c4`f0fff570 00007fff`0d744aaa     : 00000000`00000000 00000000`000000c4 00000000`00000000 00000000`00000000 : ntdll!LdrpMinimalMapModule+0x10a
000000c4`f0fff630 00007fff`0d791243     : 00000000`00000000 000000c4`f0fff719 000001ee`4fddeeb8 00000000`00000030 : ntdll!LdrpMapDllWithSectionHandle+0x1a
000000c4`f0fff680 00007fff`0d790f70     : 00000000`00000000 00000000`00000000 000001ee`4fddeeb8 000001ee`4fdd6c40 : ntdll!LdrpMapDllNtFileName+0x19f
000000c4`f0fff780 00007fff`0d79020f     : 000000c4`f0fff9b8 000001ee`4fdd6c40 000000c4`f0fffa01 000000c4`f0fff9b8 : ntdll!LdrpMapDllFullPath+0xe0
000000c4`f0fff910 00007fff`0d74fb53     : 000001ee`4fdd6c40 000000c4`f0fffa01 000000c4`00000000 000000c4`f0fffa40 : ntdll!LdrpProcessWork+0x123
000000c4`f0fff970 00007fff`0d7473e4     : 000000c4`f0fffa40 000000c4`f0fffbe0 000000c4`f0fffcd0 000000c4`f0fffbd0 : ntdll!LdrpLoadDllInternal+0x13f
000000c4`f0fff9f0 00007fff`0d746af4     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : ntdll!LdrpLoadDll+0xa8
000000c4`f0fffba0 00007fff`0b102612     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrLoadDll+0xe4
000000c4`f0fffc90 000001ee`4fd80095     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNELBASE!LoadLibraryExW+0x162
000000c4`f0fffd00 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000001ee`4fd80095


STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  unknown!noop+0

IMAGE_NAME:  unknown.dll

MODULE_NAME: Unknown_Module

FAILURE_BUCKET_ID:  SOFTWARE_NX_FAULT_c0000005_unknown.dll!noop

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {831d0811-1ea2-ade7-1bca-bc3a623ec739}

Followup:     MachineOwner
---------

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

2 participants