Ecran figé lors de l'accès aux menu sur nouvelle installation

Bonjour à tous, je suis en cours de réorganisation de ma domotique. Pour cela je suis reparti sur une installation complète (Debian 10 sous proxmox).
Mon problème est que lorsque je clique sur la barre de menu jeedom, de manière très régulière, la page est très longue à se charger, il y a parfois le logo tournant au centre de la page, j’ai fait plusieurs installation mais toujours le même problème… Lorsque j’ouvre la console Chrome, j’ai plusieurs message comme celui ci qui apparaissent au bout d’un certain temps :

DevTools failed to load SourceMap: Could not load content for http://192.168.1.54/3rdparty/jquery.contextMenu/jquery.contextMenu.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
8
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
jquery.min.js?md5=dc…1d3d4753a87c98d0a:2 [Violation] 'setTimeout' handler took 56ms

Mes connaissances sont trop limités pour interpréter cela, quelqu’un peut t-il m’éclairer ?

J’ai exactement le meme probleme et dans les meme circonstance :
Upgrade en deb 10 ( alors qu’etrangement le 4.1.5 fonctionnais encore sous 9) et j’ai des grosse longueur de chargement de page et la console chrome m’indique les même erreurs

Ça me rassure de ne pas être le seul :grin:

Pour le moment j’utilise firefox et je n’ai plus le problème