Rocket.Chat.Electron: "A JavaScript error occurred in the main process" when moving app window
My Setup
- Windows 7 64Bit, SP1.
- All updates installed
- Rocket.Chat+ v 1.3.1
- I have tested with the latest application version
- I can simulate the issue easily
Description
- After installation (update from 1.2)
- Starting the app
- Loggin in to the server
- Moving the app window
Current Behavior
Moving the app window makes an error message pop up: “A JavaScript error occurred in the main process …”
Expected Behavior
No error message
Full error message:
` [Window Title] Error
[Main Instruction] A JavaScript error occurred in the main process
[Content] Uncaught Exception: Error: EPERM: operation not permitted, rename ‘C:\Users\myusername\AppData\Roaming\Rocket.Chat+\window-state-main.json.new’ -> ‘C:\Users\myusername\AppData\Roaming\Rocket.Chat+\window-state-main.json’ at Error (native) at Object.fs.renameSync (fs.js:729:18) at writeAtomicSync (C:\Program Files (x86)\Rocket.Chat+\resources\app.asar\node_modules\fs-jetpack\lib\file_ops.js:105:8) at Object.writeSync [as write](C:Program Files %28x86%29Rocket.Chat+resourcesapp.asarnode_modulesfs-jetpacklibfile_ops.js:116:5) at Object.write (C:\Program Files (x86)\Rocket.Chat+\resources\app.asar\node_modules\fs-jetpack\lib\jetpack.js:192:21) at Object.saveState (C:\Program Files (x86)\Rocket.Chat+\resources\app.asar\background.js:72:21) at BrowserWindow.<anonymous> (C:\Program Files (x86)\Rocket.Chat+\resources\app.asar\background.js:268:25) at emitOne (events.js:77:13) at BrowserWindow.emit (events.js:169:7) [OK] `
More
- Uninstalling previous version beforehand did not solve this issue.
<bountysource-plugin>
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 1
- Comments: 38 (8 by maintainers)
Commits related to this issue
- Debounce saveState call Closes #181 — committed to RocketChat/Rocket.Chat.Electron by rodrigok 7 years ago
@tassoevan installing 2.13.3-beta1 fixes this issue for me.
@graywolf336 Working on my machine now as well.
Yes, It seems to.