Error code: STATUS_STACK_OVERFLOW when viewing Project #2082

New Issue

perfectra1n · 2023-12-19T21:55:34Z

perfectra1n commented

2023-12-19 21:55:34 +00:00

Description

Hey there,

I'm getting the following error upon attempting to load a project on v0.22.0 after migrating from v0.21.0:

I wasn't really even sure where to start, so I took a crack at using Chrome's debugger:

I'm not sure if those images are really helpful. Essentially, navigating to all the other projects in the Vikunja work just fine, but upon navigating to this one - the Chrome window/tab just becomes completely unresponsive and crashes.

I am using Typesense, Redis, and Postgres. Any tips/ideas how I might debug this weird scenario? I think I'm cursed lol. The behavior is also the same if I use an Incognito window and a different machine.

Vikunja Frontend Version

0.22.0

Vikunja API Version

0.22.0

Browser and version

120.0.6099.110 (Official Build) (64-bit) (cohort: Stable)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description Hey there, I'm getting the following error upon attempting to load a project on v0.22.0 after migrating from v0.21.0: ![image](/attachments/1c6411be-5692-4dab-8d65-392ec60ce3da) I wasn't really even sure where to start, so I took a crack at using Chrome's debugger: ![image](/attachments/c6d26696-e6f0-48b5-848e-154b189e5619) I'm not sure if those images are really helpful. Essentially, navigating to all the other projects in the Vikunja work just fine, but upon navigating to this one - the Chrome window/tab just becomes completely unresponsive and crashes. I am using Typesense, Redis, and Postgres. Any tips/ideas how I might debug this weird scenario? I think I'm cursed lol. The behavior is also the same if I use an Incognito window and a different machine. ### Vikunja Frontend Version 0.22.0 ### Vikunja API Version 0.22.0 ### Browser and version 120.0.6099.110 (Official Build) (64-bit) (cohort: Stable) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_

image.png

13 KiB

image.png

410 KiB

perfectra1n added the

kind/bug

label 2023-12-19 21:55:34 +00:00

perfectra1n commented

2023-12-19 22:04:40 +00:00

btw this is the Docker Compose that I've been trying to use to recreate what I think might've caused the issue (migrating), but I haven't been able to reproduce it yet. Hopefully it helps in the future?:

version: '3'

services:
  db:
    image: postgres:16.1
    environment:
      POSTGRES_USER: vikunja
      POSTGRES_PASSWORD: secret
      POSTGRES_DB: vikunja
    volumes:
      - ./db:/var/lib/postgresql/data
    restart: unless-stopped
  api:
    image: vikunja/api:0.22.0
    environment:
      VIKUNJA_DATABASE_HOST: db
      VIKUNJA_DATABASE_PASSWORD: secret
      VIKUNJA_DATABASE_TYPE: postgres
      VIKUNJA_DATABASE_USER: vikunja
      VIKUNJA_DATABASE_DATABASE: vikunja
      VIKUNJA_SERVICE_JWTSECRET: idk123
      VIKUNJA_SERVICE_FRONTENDURL: http://computer:90/

      VIKUNJA_TYPESENSE_ENABLED: "true"
      VIKUNJA_TYPESENSE_URL: "http://typesense:8108"
      VIKUNJA_TYPESENSE_APIKEY: "apikey123"
      
      VIKUNJA_REDIS_ENABLED: "true"
      VIKUNJA_REDIS_HOST: "redis:6379"

      VIKUNJA_LOG_DATABASE: "on"
      VIKUNJA_LOG_DATABASELEVEL: "DEBUG"
      VIKUNJA_LOG_EVENTS: "on"
      VIKUNJA_LOG_EVENTSLEVEL: "DEBUG"
      VIKUNJA_LOG_MAIL: "on"
      VIKUNJA_LOG_MAILLEVEL: "DEBUG"

      VIKUNJA_SERVICE_DEMOMODE: "true"
    volumes: 
      - ./files:/app/vikunja/files
    depends_on:
      - db
    restart: unless-stopped
  frontend:
    image: vikunja/frontend:0.22.0
    restart: unless-stopped
    environment:
      VIKUNJA_API_URL: "http://computer:90/api/v1"
  proxy:
    image: nginx
    ports:
      - 90:80
    volumes:
      - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
    depends_on:
      - api
      - frontend
      - typesense
    restart: unless-stopped
  redis:
    image: redis:7.2.3
  typesense:
    image: docker.io/typesense/typesense:0.25.1
    environment:
      TYPESENSE_API_KEY: apikey123
      TYPESENSE_DATA_DIR: "/tsdata"
    volumes:
      - ./typesense:/tsdata

btw this is the Docker Compose that I've been trying to use to recreate what I think might've caused the issue (migrating), but I haven't been able to reproduce it yet. Hopefully it helps in the future?: ```yaml version: '3' services: db: image: postgres:16.1 environment: POSTGRES_USER: vikunja POSTGRES_PASSWORD: secret POSTGRES_DB: vikunja volumes: - ./db:/var/lib/postgresql/data restart: unless-stopped api: image: vikunja/api:0.22.0 environment: VIKUNJA_DATABASE_HOST: db VIKUNJA_DATABASE_PASSWORD: secret VIKUNJA_DATABASE_TYPE: postgres VIKUNJA_DATABASE_USER: vikunja VIKUNJA_DATABASE_DATABASE: vikunja VIKUNJA_SERVICE_JWTSECRET: idk123 VIKUNJA_SERVICE_FRONTENDURL: http://computer:90/ VIKUNJA_TYPESENSE_ENABLED: "true" VIKUNJA_TYPESENSE_URL: "http://typesense:8108" VIKUNJA_TYPESENSE_APIKEY: "apikey123" VIKUNJA_REDIS_ENABLED: "true" VIKUNJA_REDIS_HOST: "redis:6379" VIKUNJA_LOG_DATABASE: "on" VIKUNJA_LOG_DATABASELEVEL: "DEBUG" VIKUNJA_LOG_EVENTS: "on" VIKUNJA_LOG_EVENTSLEVEL: "DEBUG" VIKUNJA_LOG_MAIL: "on" VIKUNJA_LOG_MAILLEVEL: "DEBUG" VIKUNJA_SERVICE_DEMOMODE: "true" volumes: - ./files:/app/vikunja/files depends_on: - db restart: unless-stopped frontend: image: vikunja/frontend:0.22.0 restart: unless-stopped environment: VIKUNJA_API_URL: "http://computer:90/api/v1" proxy: image: nginx ports: - 90:80 volumes: - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro depends_on: - api - frontend - typesense restart: unless-stopped redis: image: redis:7.2.3 typesense: image: docker.io/typesense/typesense:0.25.1 environment: TYPESENSE_API_KEY: apikey123 TYPESENSE_DATA_DIR: "/tsdata" volumes: - ./typesense:/tsdata ```

konrad commented

2023-12-19 22:11:48 +00:00

Does this only happen in Chrome? Anything particular for that project?

perfectra1n commented

2023-12-20 01:29:14 +00:00

It happens on Safari on MacOS, and on iOS via the “native webapp” (I think that’s what it’s called) that Vikunja offers:

It happens on Safari on MacOS, and on iOS via the “native webapp” (I think that’s what it’s called) that Vikunja offers: ![image](/attachments/45f51920-d7ab-41e1-b90f-eb5df64a45c4)

image.jpeg

944 KiB

perfectra1n commented

2023-12-20 03:45:16 +00:00

Nothing else weird that I can think of either, hmm

konrad commented

2023-12-20 08:36:39 +00:00

If you use the same background image on another project, does the same happen there as well?

Does it work on Firefox?

If you use the same background image on another project, does the same happen there as well? Does it work on Firefox?

perfectra1n commented

2023-12-20 23:54:21 +00:00

Same thing happens on Firefox:

When uploading the same image to another project, there doesn't seem to be any other issues...

Same thing happens on Firefox: ![image](/attachments/097d589b-c5b0-41e8-b591-f423354d435e) When uploading the same image to another project, there doesn't seem to be any other issues...

image.png

22 KiB

konrad commented

2023-12-21 13:19:58 +00:00

Is there anything in the browser console?

perfectra1n commented

2023-12-21 15:12:33 +00:00

This is what shows in the browser console upon navigating to the project:

This is what shows in the browser console upon navigating to the project: ![image](/attachments/2f433744-2d2d-4b25-a437-257c74e4df0a)

image.png

399 KiB

konrad commented

2023-12-23 13:48:54 +00:00

As suspected, the app crashes before it can log anything. Are you able to run a dev build (clone the frontend repo, install the dependencies and run pnpm serve) and point it to your api? That might give more hints. I know that's not exactly easy, but I can't really reproduce it...

https://kolaente.dev/vikunja/frontend#project-setup

As suspected, the app crashes before it can log anything. Are you able to run a dev build (clone the frontend repo, install the dependencies and run `pnpm serve`) and point it to your api? That might give more hints. I know that's not exactly easy, but I can't really reproduce it... https://kolaente.dev/vikunja/frontend#project-setup

perfectra1n commented

2023-12-23 23:36:42 +00:00

Done, you should find the --debug output attached. I navigated to the page several times, it froze, refreshed the frozen page, etc...

Done, you should find the `--debug` output attached. I navigated to the page several times, it froze, refreshed the frozen page, etc...

debug_output.txt

240 KiB

perfectra1n commented

2023-12-23 23:37:36 +00:00

I ran the command:

pnpm run serve --debug

Let me know if there's some other output that you would like to see :)

I ran the command: ```bash pnpm run serve --debug ``` Let me know if there's some other output that you would like to see :)

konrad commented

2023-12-24 13:48:01 +00:00

As far as I can tell, nothing really stood out in the debug output.

If you open the performance tab of the devtools again, do you get a source path (same spot you marked in the screenshot)?

As far as I can tell, nothing really stood out in the debug output. If you open the performance tab of the devtools again, do you get a source path (same spot you marked in the screenshot)?

konrad referenced this issue from a commit

2024-02-07 14:00:35 +00:00

chore(deps): update dependency vitest to v0.16.0 (#2082)

Sign in to join this conversation.