Opening node info leads to blank page #230

Closed
opened 2026-10-05 02:04:55 +02:00 by adam · 6 comments
Owner

When I open the node info (panel that opens from the right side) it opens for a fraction of a second and then the page goes blank. This happens to me about 75% of the time. I'm using macOS and safari. it occurs with and without content blockers.

When I open the node info (panel that opens from the right side) it opens for a fraction of a second and then the page goes blank. This happens to me about 75% of the time. I'm using macOS and safari. it occurs with and without content blockers. <!-- github-sync-id:4810631814 -->
adam closed this issue 2026-10-05 02:04:55 +02:00
Author
Owner

Is there any error in your browser console accompanying it? Is it just one node (channel or contact?) or all?

Is there any error in your browser console accompanying it? Is it just one node (channel or contact?) or all? <!-- github-comment-id:4919153674 -->
Author
Owner

It happens with all nodes. I get "Minified React error #185" 7 out of 10 times I try to view a nodes details. I see the panel open from the right then it goes blank and I have to reload and try again.

It happens with all nodes. I get "Minified React error #185" 7 out of 10 times I try to view a nodes details. I see the panel open from the right then it goes blank and I have to reload and try again. <!-- github-comment-id:4919404376 -->
Author
Owner

Just tested again with all extensions disabledand I still get the error. Chrome works well.

Just tested again with all extensions disabledand I still get the error. Chrome works well. <!-- github-comment-id:4919426046 -->
Author
Owner

Okay! Not a ton to go off of here and I can't repro locally but but I'm going to guess this is a render storm happening due to trying to render while the parent container is resizing on flyout. I'm adding a fix that will solve the issue IF that is indeed the problem; lemme know how it works for you. New docker build to come in an hour or so

Okay! Not a ton to go off of here and I can't repro locally but but I'm going to guess this is a render storm happening due to trying to render while the parent container is resizing on flyout. I'm adding a fix that will solve the issue IF that is indeed the problem; lemme know how it works for you. New docker build to come in an hour or so <!-- github-comment-id:4919989265 -->
Author
Owner

I'm gonna close this for now as tentatively resolved; if it doesn't fix for you on latest main or the version dropping in about 30 mins, feel free to reopen.

I'm gonna close this for now as tentatively resolved; if it doesn't fix for you on latest main or the version dropping in about 30 mins, feel free to reopen. <!-- github-comment-id:4920186371 -->
Author
Owner

Fixed! Thank you

Fixed! Thank you <!-- github-comment-id:4920508377 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#230