session deleted because of page crash #7
Comments
|
Maybe dont use --disable-extensions. |
I tried to remove all these and it is still the same error |
|
Try setting it to --shm-size=4g or even higher if your system allows it. |
hello , thank for reaching out. |
|
As you've mentioned using the grass image (not grass-node), please ensure you're using the latest image update. The build produced a few days ago was missing the HEADLESS=true variable, which is necessary for it to function correctly. This image is smaller and does not have a virtual display running. you can also try passing it as a docker env variable but it should already be set to true by default for the latest grass image build submitted |
|
Thanks for reply! I pulled the latest image and run w/o any addtional flags or w headless and still got the same error. The same error occurs when I run grass-node btw. |
|
docker images mrcolorrain/grass docker inspect -f '{{.Created}}' mrcolorrain/grass:latest this is should be the latest one? as I am using a docker mirror, but it should be updated. |
the latest arm64 image at the time of writing has the following manifest digest: sha256:970ceb306ee00f4768644a84fd7ce2f294e7d710963e8766294cb27bdedfbe7a and the following index digest: sha256:88939c66b7667899914fe7d0f18e00a241375d7750d9da49df1db47b1bb00ee7 |
|
I can confirm. The service is often unavailable. If the website https://app.getgrass.io/dashboard is not displayed correctly or it is not possible to log in, the extension will not work either. |
yes, that's right. A similar issue is with grass-dektop and in my case it seems to be caused by the intermittent working of grass server #5, after along time (6h) I got a 200 response from the server and the app is now working again. In grass and grass-node the app needs a well-formed DOM to work, as it needs to recognize certain elements in the website to proceed, and also the extension itself relies on the same servers to start and connect. Likewise, the desktop app does the same via websockets and so if the issue starts on the server, all flavors of grass will not work properly. I am open to PR or suggestions on how to mitigate this issue. I would also like to know if there is anything we can improve on our end in the images to make them more resilient, obviously if the issue is only server side, there is not much we can do. |
|
Thanks for pointing out the reason. The DOM of the grass site is indeed bad. Then it is hard to move on with current methodology of the code. |
I am using raspberry pi5 with 4G mem.
I use below command:
sudo docker run -d --name grass
--restart unless-stopped
--shm-size=2g
-h my_device
-e GRASS_USER=
-e GRASS_PASS=
mrcolorrain/grass
--no-sandbox
--disable-setuid-sandbox
--disable-dev-shm-usage
--headless
--disable-gpu
--disable-extensions
--disable-infobars
--disable-web-security
--disable-features=IsolateOrigins,site-per-process
and keep getting errors below
sudo docker logs -f grass
2025-01-27 04:55:46,213 - INFO - Launching Grass node application...
2025-01-27 04:56:26,828 - ERROR - An unexpected error occurred during login: Message: unknown error: session deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
(Session info: chrome=132.0.6834.110)
Stacktrace:
#0 0x555570d494c8
#1 0x555570898248
#2 0x555570887478
#3 0x5555708869f4
#4 0x5555708862f8
#5 0x555570886264
#6 0x555570884940
#7 0x555570884dd0
#8 0x555570891768
#9 0x5555708a2cf0
#10 0x555570885320
#11 0x5555708a2998
#12 0x5555709173b4
#13 0x5555708ccd6c
#14 0x5555708cd990
#15 0x555570d1ba8c
#16 0x555570d1ea80
#17 0x555570d1e634
#18 0x555570d0cfe8
#19 0x555570d1f0c0
#20 0x555570cf5f50
#21 0x555570d39244
#22 0x555570d39428
#23 0x555570d48618
#24 0x7fff841fee8c
#25 0x7fff84267b18
2025-01-27 04:56:26,828 - INFO - Retrying login... (1/3)
2025-01-27 04:56:26,840 - ERROR - An error occurred: Message: invalid session id
The text was updated successfully, but these errors were encountered: