nw.js
nw.js copied to clipboard
STATUS_ACCESS_VIOLATION.
Thanks for reporting an issue! Spend 60 seconds reading this...
- Before reporting, try reproducing against the latest version of NWJS.
- Issue tracker is only for bugs and feature requests, in English only.
Anything else? Use our mailing list for questions: https://groups.google.com/forum/#!forum/nwjs-general
======== TEMPLATE BUG FORM ========
NWJS Version : nw-v0.45.4 Operating System : windows 10 pro x64
Expected behavior
app should not crash due to unknown error.
Actual behavior
app randomly crashes due STATUS_ACCESS_VIOLATION
.
never had such problem before.
How to reproduce
theres not a fixed way to reproduce. just playin' a bit with app then it happens.
0067bdaa-fb9b-4b8e-9c62-e2f64ff235d3.zip crash dump file.
Same issue at me. I called this code.
window.location.reload();
// or
nw.Window.get().reload();
Same here: NWJS Version : sdk-0.51.1 Operating System : Windows 10
Expected behavior
Reloading the page programmatically via win.reload()
or win.reloadIgnoringCache()
or using Ctrl-R in the devtools should reload the application.
Actual behavior
-
The nw process crashes silently when devtools are closed.
-
The application crashes with an error code showing into the window: STATUS_ACCESS_VIOLATION, when devtools are opened.
How to reproduce
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="description" content="Crash test" />
<title>Crash test</title>
</head>
<body>
<script>
let win = nw.Window.get();
win.showDevTools();
setTimeout(function () {
win.reload();
}, 5000);
</script>
</body>
</html>
I also run into the same issue, but my usecase is changing the location in Javascript from http://host/abc/
to http://host/abc/xyz/
.
Any fix or workaround for this? I see this also on Windows 10, but not on mac.
Is anyone opening the window with a new_instance because that's how I got the error?
nw.Window.open('myfile.html', {new_instance: true})
then reload that window
@UtterDonkey I'm doing the same on 0.58.0
and chrome.runtime.reload()
does not bring up the new window, only closes the current one and keeps the process running. The new_instance
param has no effect.