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

Constantly Crashing #481

Open
logger24 opened this issue Jan 16, 2025 · 2 comments
Open

Constantly Crashing #481

logger24 opened this issue Jan 16, 2025 · 2 comments

Comments

@logger24
Copy link

I'd give more details, but the log file is terrible and gives zero details.
The application will randomly not respond; I alt+tab out and hover over the system tray icon and it disappears, meaning it failed to properly close cleanly.
It happens multiple times an hour and I have to keep opening it, over and over.


Faulting application name: Sidekick.exe, version: 2025.12.1759.0, time stamp: 0x67110000
Faulting module name: ntdll.dll, version: 10.0.19041.5007, time stamp: 0x688f8c4b
Exception code: 0xc0000374
Fault offset: 0x00000000000ff3c9
Faulting process id: 0x4418
Faulting application start time: 0x01db676f2a7ffb23
Faulting application path: %LOCALAPPDATA%\Sidekick\current\Sidekick.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 367c6a4c-b7af-4add-b50c-16102b5e74be
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: Sidekick.exe, version: 2025.12.1759.0, time stamp: 0x67110000
Faulting module name: ntdll.dll, version: 10.0.19041.5007, time stamp: 0x688f8c4b
Exception code: 0xc0000374
Fault offset: 0x00000000000ff3c9
Faulting process id: 0x35a4
Faulting application start time: 0x01db67bd9d28650b
Faulting application path: %LOCALAPPDATA%\Sidekick\current\Sidekick.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 8d76e474-c3c1-49dc-9e5b-4ef03e5e9728
Faulting package full name: 
Faulting package-relative application ID: 


This indicates a heap corruption, and your application is not handling something in memory properly.

@domialex
Copy link
Contributor

domialex commented Jan 16, 2025

There is only 1 known crash right now and it's #431.
Otherwise it would be your anti-virus closing the app, or windows security is suspending the app (Sidekick.exe -> properties -> look for something with either "suspended" or "came from a third party click to allow".
The Sidekick log files are in %appdata%/sidekick, paste them if you have them.

@logger24
Copy link
Author

logger24 commented Jan 16, 2025

I don't have an anti-virus, so no. I suggest otherwise.

Exception code: 0xc0000374
Fault offset: 0x00000000000ff3c9


This log file contains nothing of value, and I've found it after digging previously and looked, but sure. I'd append it.

Sidekick_log20250115.log

Albeit, I feel like minidumps would be of more value:

Sidekick.exe.16416.dmp
Sidekick.exe.16832.dmp
Sidekick.exe.17432.dmp


    Key  : Failure.Bucket
    Value: HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE_c0000374_kernel32.dll!GlobalSize
EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fff0fa6f3c9 (ntdll!RtlReportFatalFailure+0x0000000000000009)
   ExceptionCode: c0000374
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 00007fff0fad97f0

PROCESS_NAME:  Sidekick.dll

ERROR_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.

EXCEPTION_CODE_STR:  c0000374
EXCEPTION_PARAMETER1:  00007fff0fad97f0
FAULTING_THREAD:  ffffffff

STACK_TEXT:  
00007fff`0fad9848 00007fff`0fa7e081 ntdll!RtlpLogHeapFailure+0x45
00007fff`0fad9850 00007fff`0f971ecf ntdll!RtlpProbeUserBufferSafe+0x53
00007fff`0fad9858 00007fff`0f971c1a ntdll!RtlGetUserInfoHeap+0x5a
00007fff`0fad9860 00007fff`0d8081d4 kernel32!GlobalSize+0x64
00007fff`0fad9868 00007ffe`2f3daab0 unknown!unknown+0x0

STACK_COMMAND:  ** Pseudo Context ** HeapPseudo ** Value: 178777fea90 ** ; kb
SYMBOL_NAME:  kernel32!GlobalSize+64
MODULE_NAME: kernel32
IMAGE_NAME:  kernel32.dll

FAILURE_BUCKET_ID:  HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE_c0000374_kernel32.dll!GlobalSize

OS_VERSION:  10.0.19041.1
BUILDLAB_STR:  vb_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
IMAGE_VERSION:  10.0.19041.5198
FAILURE_ID_HASH:  {25511494-384a-373e-2925-15f320e45612}

I will leave you to it, and hope you can fix it in the future; thank you.

In my lay ability, I'd say the issue is you using a pointer that was previous freed, then attempted to free it again, or otherwise.

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