[BUG] Issues with a large database is back since ls337

Open
#106 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, sqlite
Domain
databases, devops

Research direction

Start by comparing v4.6.0-ls336 and v4.6.0-ls337, focusing on the SQLite upgrade from 3.51.2 to 3.53.4. Reproduce with an existing medium or large database on arm64, then verify the meal plan and recipes pages against a fresh install. Done means those pages load correctly after updating to v4.6.0-ls337.

Written by the indexing model from the issue text.

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

The problem from issue #99 is back again with version 4.6.0-ls337. The meal plan and recipes pages are not loading but show a blank page.

The culprit is most likely the recent sqlite version upgrade from 3.51.2 to 3.53.4: https://github.com/linuxserver/docker-grocy/compare/v4.6.0-ls336...v4.6.0-ls337

Expected Behavior

The meal plan and recipes page should load.

  • Reverting to 4.6.0-ls336 the pages load again.
  • A fresh install of 4.6.0-ls337 without any existing data also works.
Steps To Reproduce
  1. Simply update to version 4.6.0-ls337 and the meal plan and other pages will show a blank page when using a medium/big database instead of loading properly.
Environment

CPU architecture

arm64

Docker creation
services:
  grocy:
    #image: linuxserver/grocy:v4.5.0-ls290
    #image: linuxserver/grocy:v4.6.0-ls336
    image: linuxserver/grocy:latest
    container_name: grocy
    environment:
      - PUID=1000
      - PGID=110
      - TZ=Europe/Rome
    volumes:
      - /volume1/docker/grocy:/config
    ports:
      - 9283:80
    restart: unless-stopped
Container logs
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1024
User GID:    100
───────────────────────────────────────
Linuxserver.io version: v4.6.0-ls337
Build-date: 2026-08-23T08:01:09+00:00
───────────────────────────────────────
    
using keys found in /config/keys
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2023-08-13 │ 2026-05-04 │ /config/nginx/ssl.conf                                                 │
│ 2024-05-27 │ 2025-12-26 │ /config/nginx/nginx.conf                                               │
│ 2024-07-16 │ 2025-12-26 │ /config/nginx/site-confs/default.conf                                  │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Dominant language
Dockerfile
Stars
442
Forks
63
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxserver/docker-grocy

All issues in linuxserver/docker-grocy

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.