Nodejs/electron Override chromium browser timeout.
Been looking all over for this information, closest i can see is the
command line switches. i have a web page that i ported to electron and im trying to override the Browser inactivity timeout. for example running a report over 2 minutes the browser times out the connection. My thinking for a quick fix was to wrap in electron and extend the browser timeout.
https://peter.sh/experiments/chromium-command-line-switches/#timeout
https://github.com/electron/electron/blob/master/docs/api/chrome-command-line-switches.md
In Electron the main.js looks to have wrapped the modules in webpack
in all of the examples ive found
it looks like this
You can use app.commandLine.appendSwitch to append them in your app's main script before the ready event of the app module is emitted:
const { app } = require('electron')
app.commandLine.appendSwitch('remote-debugging-port', '8315')
app.commandLine.appendSwitch('host-rules', 'MAP * 127.0.0.1')
app.on('ready', () => {
// Your code here
})
however in my electron file my const app is actually
const path = __webpack_require__(14);
const electron = __webpack_require__(18);
const unusedFilename = __webpack_require__(20);
const pupa = __webpack_require__(23);
const extName = __webpack_require__(24);
const {app, shell} = electron;
i have tried
app.commandLine.appendSwitch("--disable-renderer-backgrounding");
app.commandLine.appendArgument('--disable-timeouts-for-profiling');
Doesnt seem to work, Any hints would be appreciated.
node.js electron chromium
asked Nov 20 '18 at 18:51
Neth MaisonNeth Maison
1
|
show 2 more comments
Been looking all over for this information, closest i can see is the
command line switches. i have a web page that i ported to electron and im trying to override the Browser inactivity timeout. for example running a report over 2 minutes the browser times out the connection. My thinking for a quick fix was to wrap in electron and extend the browser timeout.
https://peter.sh/experiments/chromium-command-line-switches/#timeout
https://github.com/electron/electron/blob/master/docs/api/chrome-command-line-switches.md
In Electron the main.js looks to have wrapped the modules in webpack
in all of the examples ive found
it looks like this
You can use app.commandLine.appendSwitch to append them in your app's main script before the ready event of the app module is emitted:
const { app } = require('electron')
app.commandLine.appendSwitch('remote-debugging-port', '8315')
app.commandLine.appendSwitch('host-rules', 'MAP * 127.0.0.1')
app.on('ready', () => {
// Your code here
})
however in my electron file my const app is actually
const path = __webpack_require__(14);
const electron = __webpack_require__(18);
const unusedFilename = __webpack_require__(20);
const pupa = __webpack_require__(23);
const extName = __webpack_require__(24);
const {app, shell} = electron;
i have tried
app.commandLine.appendSwitch("--disable-renderer-backgrounding");
app.commandLine.appendArgument('--disable-timeouts-for-profiling');
Doesnt seem to work, Any hints would be appreciated.
node.js electron chromium
asked Nov 20 '18 at 18:51
Neth MaisonNeth Maison
1
Why not put the heavy lifting in a service worker and do it all asynchronously? Waiting 2 minutes for the window to finish rendering just seems like bad UX.
– Tiny Giant
Nov 20 '18 at 19:02
Agree completely, this is a quick fix as the devs for the Web app wont have this done in months. issues lie in the database query taking extremely long time.
– Neth Maison
Nov 20 '18 at 20:00
Why can't you initiate the database call after the initial page load?
– Tiny Giant
Nov 20 '18 at 20:14
the database call is what populates the data table that the page will load. it takes over 2 minutes. the app is currently in .net and will be changed over eventually because of that dev changes are not high priority.
– Neth Maison
Nov 20 '18 at 23:58
Have yourindex.htmluse anXMLHttpRequestto the page that does the database call.XHR's don't have a timeout by default. Then theindex.htmlpage loads immediately, and doesn't block the main thread. No hacking of Electron required.
– Tiny Giant
Nov 21 '18 at 0:08
|
show 2 more comments
Been looking all over for this information, closest i can see is the
command line switches. i have a web page that i ported to electron and im trying to override the Browser inactivity timeout. for example running a report over 2 minutes the browser times out the connection. My thinking for a quick fix was to wrap in electron and extend the browser timeout.
https://peter.sh/experiments/chromium-command-line-switches/#timeout
https://github.com/electron/electron/blob/master/docs/api/chrome-command-line-switches.md
In Electron the main.js looks to have wrapped the modules in webpack
in all of the examples ive found
it looks like this
You can use app.commandLine.appendSwitch to append them in your app's main script before the ready event of the app module is emitted:
const { app } = require('electron')
app.commandLine.appendSwitch('remote-debugging-port', '8315')
app.commandLine.appendSwitch('host-rules', 'MAP * 127.0.0.1')
app.on('ready', () => {
// Your code here
})
however in my electron file my const app is actually
const path = __webpack_require__(14);
const electron = __webpack_require__(18);
const unusedFilename = __webpack_require__(20);
const pupa = __webpack_require__(23);
const extName = __webpack_require__(24);
const {app, shell} = electron;
i have tried
app.commandLine.appendSwitch("--disable-renderer-backgrounding");
app.commandLine.appendArgument('--disable-timeouts-for-profiling');
Doesnt seem to work, Any hints would be appreciated.
node.js electron chromium
asked Nov 20 '18 at 18:51
Neth MaisonNeth Maison
1
Been looking all over for this information, closest i can see is the
command line switches. i have a web page that i ported to electron and im trying to override the Browser inactivity timeout. for example running a report over 2 minutes the browser times out the connection. My thinking for a quick fix was to wrap in electron and extend the browser timeout.
https://peter.sh/experiments/chromium-command-line-switches/#timeout
https://github.com/electron/electron/blob/master/docs/api/chrome-command-line-switches.md
In Electron the main.js looks to have wrapped the modules in webpack
in all of the examples ive found
it looks like this
You can use app.commandLine.appendSwitch to append them in your app's main script before the ready event of the app module is emitted:
const { app } = require('electron')
app.commandLine.appendSwitch('remote-debugging-port', '8315')
app.commandLine.appendSwitch('host-rules', 'MAP * 127.0.0.1')
app.on('ready', () => {
// Your code here
})
however in my electron file my const app is actually
const path = __webpack_require__(14);
const electron = __webpack_require__(18);
const unusedFilename = __webpack_require__(20);
const pupa = __webpack_require__(23);
const extName = __webpack_require__(24);
const {app, shell} = electron;
i have tried
app.commandLine.appendSwitch("--disable-renderer-backgrounding");
app.commandLine.appendArgument('--disable-timeouts-for-profiling');
Doesnt seem to work, Any hints would be appreciated.
node.js electron chromium
node.js electron chromium
asked Nov 20 '18 at 18:51
Neth MaisonNeth Maison
1
asked Nov 20 '18 at 18:51
Neth MaisonNeth Maison
1
asked Nov 20 '18 at 18:51
Neth MaisonNeth Maison
1
asked Nov 20 '18 at 18:51
Neth MaisonNeth Maison
1
asked Nov 20 '18 at 18:51
Neth MaisonNeth Maison
1
1
Why not put the heavy lifting in a service worker and do it all asynchronously? Waiting 2 minutes for the window to finish rendering just seems like bad UX.
– Tiny Giant
Nov 20 '18 at 19:02
Agree completely, this is a quick fix as the devs for the Web app wont have this done in months. issues lie in the database query taking extremely long time.
– Neth Maison
Nov 20 '18 at 20:00
Why can't you initiate the database call after the initial page load?
– Tiny Giant
Nov 20 '18 at 20:14
the database call is what populates the data table that the page will load. it takes over 2 minutes. the app is currently in .net and will be changed over eventually because of that dev changes are not high priority.
– Neth Maison
Nov 20 '18 at 23:58
Have yourindex.htmluse anXMLHttpRequestto the page that does the database call.XHR's don't have a timeout by default. Then theindex.htmlpage loads immediately, and doesn't block the main thread. No hacking of Electron required.
– Tiny Giant
Nov 21 '18 at 0:08
|
show 2 more comments
Why not put the heavy lifting in a service worker and do it all asynchronously? Waiting 2 minutes for the window to finish rendering just seems like bad UX.
– Tiny Giant
Nov 20 '18 at 19:02
Agree completely, this is a quick fix as the devs for the Web app wont have this done in months. issues lie in the database query taking extremely long time.
– Neth Maison
Nov 20 '18 at 20:00
Why can't you initiate the database call after the initial page load?
– Tiny Giant
Nov 20 '18 at 20:14
the database call is what populates the data table that the page will load. it takes over 2 minutes. the app is currently in .net and will be changed over eventually because of that dev changes are not high priority.
– Neth Maison
Nov 20 '18 at 23:58
Have yourindex.htmluse anXMLHttpRequestto the page that does the database call.XHR's don't have a timeout by default. Then theindex.htmlpage loads immediately, and doesn't block the main thread. No hacking of Electron required.
– Tiny Giant
Nov 21 '18 at 0:08
Why not put the heavy lifting in a service worker and do it all asynchronously? Waiting 2 minutes for the window to finish rendering just seems like bad UX.
– Tiny Giant
Nov 20 '18 at 19:02
Why not put the heavy lifting in a service worker and do it all asynchronously? Waiting 2 minutes for the window to finish rendering just seems like bad UX.
– Tiny Giant
Nov 20 '18 at 19:02
Agree completely, this is a quick fix as the devs for the Web app wont have this done in months. issues lie in the database query taking extremely long time.
– Neth Maison
Nov 20 '18 at 20:00
Agree completely, this is a quick fix as the devs for the Web app wont have this done in months. issues lie in the database query taking extremely long time.
– Neth Maison
Nov 20 '18 at 20:00
Why can't you initiate the database call after the initial page load?
– Tiny Giant
Nov 20 '18 at 20:14
Why can't you initiate the database call after the initial page load?
– Tiny Giant
Nov 20 '18 at 20:14
the database call is what populates the data table that the page will load. it takes over 2 minutes. the app is currently in .net and will be changed over eventually because of that dev changes are not high priority.
– Neth Maison
Nov 20 '18 at 23:58
the database call is what populates the data table that the page will load. it takes over 2 minutes. the app is currently in .net and will be changed over eventually because of that dev changes are not high priority.
– Neth Maison
Nov 20 '18 at 23:58
Have your
index.html use an XMLHttpRequest to the page that does the database call. XHR's don't have a timeout by default. Then the index.html page loads immediately, and doesn't block the main thread. No hacking of Electron required.– Tiny Giant
Nov 21 '18 at 0:08
Have your
index.html use an XMLHttpRequest to the page that does the database call. XHR's don't have a timeout by default. Then the index.html page loads immediately, and doesn't block the main thread. No hacking of Electron required.– Tiny Giant
Nov 21 '18 at 0:08
|
show 2 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53399643%2fnodejs-electron-override-chromium-browser-timeout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53399643%2fnodejs-electron-override-chromium-browser-timeout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why not put the heavy lifting in a service worker and do it all asynchronously? Waiting 2 minutes for the window to finish rendering just seems like bad UX.
– Tiny Giant
Nov 20 '18 at 19:02
Agree completely, this is a quick fix as the devs for the Web app wont have this done in months. issues lie in the database query taking extremely long time.
– Neth Maison
Nov 20 '18 at 20:00
Why can't you initiate the database call after the initial page load?
– Tiny Giant
Nov 20 '18 at 20:14
the database call is what populates the data table that the page will load. it takes over 2 minutes. the app is currently in .net and will be changed over eventually because of that dev changes are not high priority.
– Neth Maison
Nov 20 '18 at 23:58
Have your
index.htmluse anXMLHttpRequestto the page that does the database call.XHR's don't have a timeout by default. Then theindex.htmlpage loads immediately, and doesn't block the main thread. No hacking of Electron required.– Tiny Giant
Nov 21 '18 at 0:08