ahbeng
ahbeng
IImmich
Created by ahbeng on 4/23/2025 in #help-desk-support
Feature: Make the Mobile Web Timeline "Arrows" (v 1.132.0) catch for bigger thumbs
Kudos: This is a long time coming (v1.132.0) and love the new mobile web optimizations and the new timeline scrolling. Loved how pretty, optimized with dynamic layouts (not just 2 large pictures per row) and how smooth it is! Problem: I have huge thumbs and the new web timeline scrolling arrows doesn't seem to catch (nor like) my thumb. Proposal: Enlarge the "catch" section of the timeline scrolling arrows or even catch when pressing the pop-up date of the timeline to allow my big thumbs to scroll the timeline. Thank you! Thank you!
4 replies
IImmich
Created by ahbeng on 5/27/2023 in #help-desk-support
Immich-Proxy timing out for 1st time setup Android app "Building Timeline"
It seems that the nginx timing out for a first time setup of the Immich Android app. Getting these in the Immich-Proxy logs: 2023/05/27 02:10:14 [error] 40#40: *196 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.147.17.20, server: , request: "GET /api/asset HTTP/1.1", upstream: "http://172.18.0.7:3001/asset", host: "10.147.17.2:2283" I tried to update the /etc/nginx/conf.d/default.conf file but I can't as its not writable with the nginx user.
55 replies
IImmich
Created by ahbeng on 3/30/2023 in #help-desk-support
Getting Javascript Heap out of Memory quite often since 1.52.0 and 1.52.1
HI all, I've been getting this quite often in the Immich-Microservice container. It's been happening quite often now after 1.52.0 and 1.52.1. Especially on the Storage Migration jobs and now at the Generate Thumbnails jobs. I'm assuming its not fully migrated yet to the new folders, so I'll try to let it run more until I hope it'll completely migrated. <--- Last few GCs ---> [1:0x7fb16cefc330] 793094 ms: Scavenge (reduce) 2038.1 (2076.2) -> 2037.5 (2076.5) MB, 21.1 / 0.0 ms (average mu = 0.352, current mu = 0.391) allocation failure [1:0x7fb16cefc330] 794130 ms: Scavenge (reduce) 2038.3 (2076.5) -> 2037.7 (2076.5) MB, 39.0 / 0.0 ms (average mu = 0.352, current mu = 0.391) allocation failure [1:0x7fb16cefc330] 795665 ms: Scavenge (reduce) 2038.5 (2076.5) -> 2038.0 (2076.7) MB, 66.7 / 0.1 ms (average mu = 0.352, current mu = 0.391) allocation failure <--- JS stacktrace ---> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory I recall something about allocating the heap for Node.js b4... can't remember how I set that up that param.
12 replies