Rocket.chat.electron: Moving the application window throws error dialog

Created on 11 May 2016  路  14Comments  路  Source: RocketChat/Rocket.Chat.Electron

Originally posted from @nmummau at https://github.com/RocketChat/Rocket.Chat/issues/3181
Your Rocket.Chat version: 1.3.1
Windows 7 Professional

When I click and drag the title bar of the application to move the window, I get an error window. Literally whenever I move the window a few inches it throws the error. If I acknowledge the error dialog, and then move the application, the error is thrown again.

image

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Most helpful comment

I believe i solved my issue by adding an exception to my antivirus(mcafee), and it now works perfectly!

All 14 comments

@nmummau does this happen immediately after starting the application up?

Like if you kill it completely (make sure its not in task bar, or there aren't more then on in task bar) then start it. How long before this happens?

same on windows10. Error appears right after application start.

@geekgonecrazy no it doesn't happen immediately for me. It requires me to try to move the window around.

@nmummau you are right. You need to move the window to trigger the error.

I'm getting the same issue, it also happen when minimising it

Many of my colleagues have this issue. Any update on resolving it?

I believe i solved my issue by adding an exception to my antivirus(mcafee), and it now works perfectly!

Similar to @nobodyshome, with McAfee, we allowed for C:\Users\*\AppData\Roaming\Rocket.Chat+\window-state-main.json to be excluded and we no longer have this issue.

Confirmed, with an exception in the McAfee on-access scanner the client stops throwing JavaScript exceptions.

@geekgonecrazy can you test this again?

Maybe we should add @richardwlu fix on our documentation?

@geekgonecrazy can you test this again?

Last build I tested on windows I never had this happen. So I think it might be solved other then the edge case with McAfee

I agree, I think we can close this out. I haven't seen it since I reported it in May 2016.

Was this page helpful?
0 / 5 - 0 ratings