calendar -> deck -> deck card sequence freezes browser for minute
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 22/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- javascript
- Área
- frontend, performance
Línea de trabajo
The payload names no source files. Start by reproducing the freeze: open Calendar, switch to Deck, then open a card, and watch the browser network and performance panels. The only evidence is an HAR archive linked in the report, and the body has unfilled placeholders where logs should be. Done means identifying which request or render step blocks for about a minute and fixing it without regressing card opening. Because this is a performance bug in a cross-app flow, ask a maintainer for the expected scope before you start.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Describe the bug
WHen i browse calendar then switch to deck and then to particular deck card it freezes browser for a minute so it's start displaying the warning about site freezing browser
To Reproduce
Steps to reproduce the behavior:
- Go to Calendar
- Go to Deck and select any card there
- See browser showing error and debug net view showing almost 1,5minute freeze
Client details:
- OS: Linux, Windows10
- Browser : Firefox and Chrome
- Version Current latest 34.0.4
- Device: desktop
SEE HTTP LOG :
Operating system:
Nextcloud snap
Web server:
Nextcloud snap
Database:
Nextcloud snap
PHP version:
Nextcloud snap
Nextcloud version: (see Nextcloud admin page)
Nextcloud snap
Where did you install Nextcloud from:
Nextcloud snap
Signing status:
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
No errors have been found.
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Nextcloud configuration:
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:
HAR file
[192.168.100.239_Archive \[26-10-16 15-08-46\].tar.gz](https://github.com/user-attachments/files/33547608/192.168.100.239_Archive.26-10-16.15-08-46.tar.gz)
a) The javascript console log
b) The network log
c) ...
- Lenguaje dominante
- JavaScript
- Estrellas
- 1.4k
- Forks
- 358
- Merge medio
- 2 d 18 h
- PR fusionados (30 d)
- 83
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nextcloud/deck
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
CSV export leaves trailing commas in tags and assigned-user fieldsPosiblemente ocupada @Kumar-s75 la tomó hace 39 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Board clone API failure is treated as a successful board responsePosiblemente ocupada @Kumar-s75 la tomó hace 39 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nextcloud/deck#8334 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
1. to develop bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nextcloud/deck#8146 · 2 comentarios · 2 reacciones ·
Los mantenedores suelen responder en 1 día
Todos los issues de nextcloud/deck
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
gkjohnson/three-mesh-bvh#933 ·
-
scope: curriculum status: waiting triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
freeCodeCamp/freeCodeCamp#71076 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
HarperFast/harper#3275 ·
Los mantenedores suelen responder en 1 día
-
liveQuery: a late rejection from an aborted (superseded) query run still reaches observer.errorAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
documentation good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
steerion-labs/bounded-agent-runtime#93 ·
Los mantenedores suelen responder en 1 día