github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-15 22:54:03 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[Bug]: Crash during sync – Fatal error: Check failed: CodeKindCanDeoptimize(code.kind()) #2050

New Issue
Closed
opened 2026-02-28 20:02:05 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:02:05 -06:00
Owner
Copy Link

Originally created by @skefre on GitHub (Apr 15, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Hi! 👋 I'm running ActualBudget on Pikapod (Docker-based) and experiencing a crash every time I try to sync. The UI shows a successful POST /sync/sync, but the sync silently fails. Looking at the container logs, I can see a fatal V8 error that seems to crash the sync process.

How can we reproduce the issue?

Steps to Reproduce:

Deploy ActualBudget using the official Docker image (latest version).
Go to Settings > Sync and enable syncing.
Click "Sync" on any account.
Sync spins briefly, then nothing happens – logs show a fatal crash.

Expected Behavior: Sync should complete and update accounts with changes.

Actual Behavior: Sync appears to start but crashes with a V8 fatal error (see log below).

Log Output:

Fatal error in , line 0

Check failed: CodeKindCanDeoptimize(code.kind()).

#FailureMessage Object: 0x7fff12c3ea70
1: 0xc06c31 [node]
2: 0x1ecb334 V8_Fatal(char const*, ...) [node]
3: 0xe79a41 v8::internal::Deoptimizer::DeoptimizeMarkedCodeForContext(v8::internal::NativeContext) [node]
...
14: 0xffcd70 v8::internal::StoreIC::Store(v8::internal::Handlev8::internal::Object, v8::internal::Handlev8::internal::Name, v8::internal::Handlev8::internal::Object, v8::internal::StoreOrigin) [node]
15: 0xffd104 v8::internal::Runtime_StoreIC_Miss(int, unsigned long*, v8::internal::Isolate*) [node]
16: 0x1711cb9 [node]

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Safari

Operating System

None

Originally created by @skefre on GitHub (Apr 15, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Hi! 👋 I'm running ActualBudget on Pikapod (Docker-based) and experiencing a crash every time I try to sync. The UI shows a successful POST /sync/sync, but the sync silently fails. Looking at the container logs, I can see a fatal V8 error that seems to crash the sync process. ### How can we reproduce the issue? Steps to Reproduce: Deploy ActualBudget using the official Docker image (latest version). Go to Settings > Sync and enable syncing. Click "Sync" on any account. Sync spins briefly, then nothing happens – logs show a fatal crash. Expected Behavior: Sync should complete and update accounts with changes. Actual Behavior: Sync appears to start but crashes with a V8 fatal error (see log below). Log Output: # Fatal error in , line 0 # Check failed: CodeKindCanDeoptimize(code.kind()). #FailureMessage Object: 0x7fff12c3ea70 1: 0xc06c31 [node] 2: 0x1ecb334 V8_Fatal(char const*, ...) [node] 3: 0xe79a41 v8::internal::Deoptimizer::DeoptimizeMarkedCodeForContext(v8::internal::NativeContext) [node] ... 14: 0xffcd70 v8::internal::StoreIC::Store(v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Name>, v8::internal::Handle<v8::internal::Object>, v8::internal::StoreOrigin) [node] 15: 0xffd104 v8::internal::Runtime_StoreIC_Miss(int, unsigned long*, v8::internal::Isolate*) [node] 16: 0x1711cb9 [node] ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Safari ### Operating System None
GiteaMirror added the can’t replicatewontfixbug labels 2026-02-28 20:02:05 -06:00
GiteaMirror commented 2026-02-28 20:02:05 -06:00
Author
Owner
Copy Link

@alecbakholdin commented on GitHub (May 2, 2025):

Is this still happening? Frankly this seems outside our area of expertise and likely not related to Actual. I'm not even sure where to begin looking for this

@alecbakholdin commented on GitHub (May 2, 2025): Is this still happening? Frankly this seems outside our area of expertise and likely not related to Actual. I'm not even sure where to begin looking for this
GiteaMirror commented 2026-02-28 20:02:06 -06:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 4, 2025):

I'm going to close this off as I can't replicate and we'll need more info to move forward with it.

@matt-fidd commented on GitHub (Jun 4, 2025): I'm going to close this off as I can't replicate and we'll need more info to move forward with it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug can’t replicate wontfix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2050
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?