Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java Script Error: ERR_IPC_CHANNEL_CLOSED #939

Open
JuanRaVa opened this issue Jan 23, 2025 · 8 comments
Open

Java Script Error: ERR_IPC_CHANNEL_CLOSED #939

JuanRaVa opened this issue Jan 23, 2025 · 8 comments

Comments

@JuanRaVa
Copy link

Hi guys,

I'm getting this error in the last days. It can happen at starting of OS Windows or when you go to the slider and try to move but the slider is disable, after that in about 10 min I get the error. Below the picture about the error and the slider disable.

Image

Image

Please if you need more info don't hesitate to contact me,

Thank you,

@wiljums
Copy link

wiljums commented Jan 23, 2025

Same here.

@sgilder1
Copy link

Also for me

@eurofjr
Copy link

eurofjr commented Feb 2, 2025

exact same for me as well. The error is inconsistent but occurs most often after period of inactivity. For example, if lock screen and come back to the computer after a couple of hours, error seems to happen. If I restart the computer, no error.

This is on updated Windows 11.

@finalgamer
Copy link

finalgamer commented Feb 6, 2025

To me this happens when the screens go to sleep and when I come back to the PC and wake it again it immediately shows this error about 5 times. The app still works however.

@webash
Copy link

webash commented Feb 6, 2025

To me this happens when the screens go to sleep and when I come back to the PC and wake it again it immediately shows this error about 5 times. The app still works however.

This is also my problem. No hardware changes. Only thing that I can think is some kind of Windows Update that might have been applied.

Any deeper logs we can retrieve to help diagnose?

@eurofjr
Copy link

eurofjr commented Feb 8, 2025

I should add that, for me, lock screen also includes physically turning off the monitors (at least for the times where this error occurs). Taken in conjunction with webash's and finalgamer's comments, the state of the monitors or how TwinkleTray detects them could be a factor in the errors.

Additionally, I had a different "error" today but one that occurred after I turned my monitors back on and woke the computer from a locked state. Rather than being a separate issue, the similar conditions makes me think that this could be related. After I turned the monitors on and unlocked the computer, TwinkleTray (TT) only recognized the primary monitor, of my three monitors. My setup involves a laptop screen and two monitors connected via a hub with the primary monitor being one connected via the hub. At some point, maybe 10-15 minutes later, I checked TT again and all three monitors were now showing back up as they normally do.

I'd be happy to submit logs if they might be helpful.

@milanmpetrovic
Copy link

Same here :(

@bel57
Copy link

bel57 commented Feb 22, 2025

Ditto
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants