SIGILL in browser when uploading large directory of photos

[samvv]

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

• Yes

The bug

When moving my freshly downloaded Google Photos folder over from the file explorer to the web client in the Brave browser (shields off), Immich freezes and continues to be frozen for several minutes, until this screen appears:

This has been tested on both GNOME with Nautilus and COSMIC with COSMIC Files.

The OS that Immich Server is running on

Kubernetes on Ubuntu Server 24.04

Version of Immich Server

v2.7.5

Version of Immich Mobile App

2.7.4.build.3045

Platform with the issue

• Server
• Web
• Mobile

Device make and model

Samsung Galaxy A16

Your docker-compose.yml content

Not applicable since I use Helm.

Your .env content

Not applicable since I use Helm.

Reproduction steps

1. Install the Immich Helm chart
2. Create an admin account
3. Drag and drop a large folder to the main page of the web client

Relevant log output

Additional information

Tested on Arch Linux with all packages up-to-date.

The folder with photos is 4,7 GiB large.

From what I can tell there no API request is reaching the server and this is purely a web client bug.

[samvv]

Found the culprit: it's the JSON files from the Google Takeout wreaking havoc. Doing a find -name '*.json' -delete inside the folder fixed it for me.

Still would be nice if Immich would handle this case automatically, though.

[upmcplanetracker]

Do you know what specifically in the json was causing the problem? Can you attach it here so the developers and others can look at it. If they know the problematic part of the json file someone could presumably run a check to see if the offender is in the file and the strip it out before importing photos.

[samvv]

My guess is there were A LOT of small JSON files (1 for each photo), and for each JSON file Svelte was creating a UI message saying that the file was not recognised. This caused a huge allocaction of DOM elements and memory exhaustion, hence the SIGILL.

[samvv]

The directory is uploading just fine right now after I removed all the JSON files.

[upmcplanetracker]

This is a good explanation and makes sense. Thanks. Is there a reason to have json files created by Google photos takeout when importing then into immich? If not, wonder if immich could pre check for Google photos json files and strip them out / not include them?

…

On Sun, Jun 7, 2026, 9:42 AM Sam Vervaeck ***@***.***> wrote: *samvv* left a comment (immich-app/immich#28895) <#28895 (comment)> My guess is there were A LOT of small JSON files (1 for each photo), and for each JSON file Svelte was creating a UI message saying that the file was not recognised. This caused a huge allocaction of DOM elements and memory exhaustion, hence the SIGILL. -------- Original Message -------- On Sunday, 06/07/26 at 15:35 upmcplanetracker ***@***.***> wrote: > upmcplanetracker left a comment [(immich-app/immich#28895)]( #28895 (comment)) > > Do you know what specifically in the json was causing the problem? Can you attach it here so the developers and others can look at it. If they know the problematic part of the json file someone could presumably run a check to see if the offender is in the file and the strip it out before importing photos. > > — > Reply to this email directly, [view it on GitHub]( #28895?email_source=notifications&email_token=AOJSQVUFCHZY3OCPUXDXJR346VVSNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGI4DENRYGM22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4642826835), or [unsubscribe]( https://github.com/notifications/unsubscribe-auth/AOJSQVXOULDI4MRODBAY5T346VVSNAVCNFSM6AAAAACZ55SSEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNBSHAZDMOBTGU ). > You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#28895?email_source=notifications&email_token=BUKFPFGP7OYELB2LXAMTCC346VWL5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGI4DINBXHA22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4642844785>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BUKFPFDUUHFOTY7FZA6PM3T46VWL5AVCNFSM6AAAAACZ55SSEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNBSHA2DINZYGU> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BUKFPFASJCL5UCZZJF4QVOD46VWL5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGI4DINBXHA22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BUKFPFAUC4PZNKJBVWBUQEL46VWL5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGI4DINBXHA22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[samvv]

Detecting that might be hard because nothing explicitly marks the folder as a Google Takeout AFAICT.

Maybe instead of displaying a message at each unrecognised file we can keep track of a counter and something like a small expandable table that is asynchronousy updated as files are discovered? The table could be lazily loaded to avoid large allocations of DOM elements.

As for why Google does this: I have no idea; I just used the default settings which were not adjustable.

[bo0tzz]

FYI, for uploading a takeout you probably want to use https://github.com/simulot/immich-go instead.

[samvv]

Oh whoops of course there's a tool for that.

[upmcplanetracker]

I'm sure it's from Google's own internal record keeping and it just gets packaged up with every takeout.

…

On Sun, Jun 7, 2026, 9:49 AM Sam Vervaeck ***@***.***> wrote: *samvv* left a comment (immich-app/immich#28895) <#28895 (comment)> Detecting that might be hard because nothing explicitly marks the folder as a Google Takeout AFAICT. Maybe instead of displaying a message at each unrecognised file we can keep track of a counter and something like a small expandable table that is asynchronousy updated as files are discovered? The table could be lazily loaded to avoid large allocations of DOM elements. As for why Google does this: I have no idea; I just used the default settings which were not adjustable. — Reply to this email directly, view it on GitHub <#28895?email_source=notifications&email_token=BUKFPFHFUFQVWSJGY5CMZV346VXFRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGI4DMMBTGE3KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4642860316>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BUKFPFHD4MYRVTAGOQ3PKN346VXFRAVCNFSM6AAAAACZ55SSEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNBSHA3DAMZRGY> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BUKFPFAJCOJ4NGY4XEXT45L46VXFRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGI4DMMBTGE3KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BUKFPFHXD47FPJAY4FQQNDL46VXFRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGI4DMMBTGE3KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>