Nightmare Js Evaluation timed out after multiple evaluations











up vote
1
down vote

favorite












I'm trying to setup an app I've been developing that involves recording an HTML widget (with animations) and turning it into an mp4. Locally it works great. I have Nightmare Js handling the screenshots and FFMPEG converting the screenshots into an mp4, which takes around 90s on my PC.



I'm setting it up in a docker container through a hosting service, and cannot get past this issue. My test script at the moment looks something like this:



const Nightmare = require('nightmare')

const Xvfb = require('xvfb')



module.exports = function(app) {

  app.get('/api/nightmare', async (req, res) => {

    console.log('GET request to /api/nightmare')



    try {

      // Start xvfb and create our nightmare object

      const close = await xvfb()

      const nightmare = Nightmare({ executionTimeout: 1000 })



      const [err, result] = await poss(run(nightmare))

      if (err) {

        // Cleanup before throwing error

        await nightmare.end()

        await close()

        throw err

      }



      // shut'er down

      await nightmare.end()

      await close()

      res.status(200).send('Completed')

    } catch (error) {

      console.log(error)

      res.status(500).send(error)

    }

  })  

}



async function run(nightmare) {

  var data = {

    'id': '2OWBTMUL',

    'somedata': 'blah'

    // More data pulled from the database goes here

  }



  // Create folder to hold images

  var procName = new Date().getTime() + '_testing_' + data.id

  fs.mkdirSync(path.resolve(__dirname, '../processing/', procName))



  // URL to inject into webpage so the webpage can access the data

  var url = `http://example.com?` +

    `id=${data.id}&` +

    `somedata=${data.somedata}`



  console.log('Starting NightmareJs')

  await nightmare

    .viewport(1920, 1080)

    .goto('file:///' + path.resolve(__dirname, '../templates/example.html'))

    .evaluate(newUrl => {

      // Set url and get the page ready for recording

      url = new URL(newUrl)

      initiate()

      start()

      timeline.pause()

    }, url)

    .catch(error => { console.log(error) })



  // Take 200 screenshots (8s @ 25fps)

  var frames = 200

  for (var i = 0; i < frames; i++) {

    console.log('Taking screenshot ' + i)



    await nightmare

      .screenshot(path.resolve(__dirname, '../processing/', procName, 'screen_' + i + '.png'))

      .evaluate(shot => { timeline.seek((8 / 200) * shot) }, i)

      .catch(error => { console.log(error) })

  }



  console.log('Done.')

}



// xvfb wrapper

function xvfb(options) {

  var xvfb = new Xvfb(options)



  function close() {

    return new Promise((resolve, reject) => {

      xvfb.stop(err => (err ? reject(err) : resolve()))

    })

  }



  return new Promise((resolve, reject) => {

    xvfb.start(err => (err ? reject(err) : resolve(close)))

  })

}



// try/catch helper

async function poss(promise) {

  try {

    const result = await promise

    return [null, result]

  } catch (err) {

    return [err, null]

  }

}


Some environment details:

Ubuntu 18.04.1

Supervisor

Node 8.12.0 (DEBUG=* set)



The issue:
After about 17 loops, Nightmare throws two different errors.
In my nodejs-stderr.log file, I get this



Taking screenshot x

Error: Evaluation timed out after 1000msec.  Are you calling done() or resolving your promises?


Testing with the done() callback or promise in the evaluation didn't change anything, so I kept it simple



In my nodejs-stdout.log file, I get this for every successful loop



Mon, 19 Nov 2018 09:37:06 GMT nightmare:actions .screenshot()

Mon, 19 Nov 2018 09:37:06 GMT nightmare:log subscribing to browser window frames

Mon, 19 Nov 2018 09:37:06 GMT nightmare:log Highlighting page to trigger rendering.

Mon, 19 Nov 2018 09:37:06 GMT nightmare:log unsubscribing from browser window frames

Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .screenshot() captured with length 1092963

Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .evaluate() fn on the page

Mon, 19 Nov 2018 09:37:07 GMT nightmare queueing action "screenshot"

Mon, 19 Nov 2018 09:37:07 GMT nightmare queueing action "evaluate"

Mon, 19 Nov 2018 09:37:07 GMT nightmare running


And then after 17 or so loops, I get:



Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .screenshot()

Mon, 19 Nov 2018 09:37:07 GMT nightmare:log subscribing to browser window frames

Mon, 19 Nov 2018 09:37:07 GMT nightmare:log Highlighting page to trigger rendering.

Tue, 20 Nov 2018 02:11:43 GMT nightmare:log crashed [{},false]

Mon, 19 Nov 2018 09:37:12 GMT nightmare:log FrameManager timing out after 1000 ms with no new rendered frames

Mon, 19 Nov 2018 09:37:12 GMT nightmare:log unsubscribing from browser window frames

Mon, 19 Nov 2018 09:37:12 GMT nightmare:actions .screenshot() captured with length 0

Mon, 19 Nov 2018 09:37:12 GMT nightmare:actions .evaluate() fn on the page

Mon, 19 Nov 2018 09:37:13 GMT nightmare queueing action "screenshot"

Mon, 19 Nov 2018 09:37:13 GMT nightmare queueing action "evaluate"

Mon, 19 Nov 2018 09:37:13 GMT nightmare running


And the rest all fail, without the crashed [{},false] message.

Removing .evaluate(shot => { timeline.seek((8 / 200) * shot) }, i) in the loop solves the issue, but I need that otherwise it's just a motionless video! I have tried separate calls (not chaining evaluate and screenshot), putting .wait(200) between stuff, but I can't figure it out or find any help on this issue.






javascript node.js electron nightmare







share|improve this question




























    up vote
    1
    down vote

    favorite












    I'm trying to setup an app I've been developing that involves recording an HTML widget (with animations) and turning it into an mp4. Locally it works great. I have Nightmare Js handling the screenshots and FFMPEG converting the screenshots into an mp4, which takes around 90s on my PC.



    I'm setting it up in a docker container through a hosting service, and cannot get past this issue. My test script at the moment looks something like this:



    const Nightmare = require('nightmare')
    
const Xvfb = require('xvfb')
    

    
module.exports = function(app) {
    
  app.get('/api/nightmare', async (req, res) => {
    
    console.log('GET request to /api/nightmare')
    

    
    try {
    
      // Start xvfb and create our nightmare object
    
      const close = await xvfb()
    
      const nightmare = Nightmare({ executionTimeout: 1000 })
    

    
      const [err, result] = await poss(run(nightmare))
    
      if (err) {
    
        // Cleanup before throwing error
    
        await nightmare.end()
    
        await close()
    
        throw err
    
      }
    

    
      // shut'er down
    
      await nightmare.end()
    
      await close()
    
      res.status(200).send('Completed')
    
    } catch (error) {
    
      console.log(error)
    
      res.status(500).send(error)
    
    }
    
  })  
    
}
    

    
async function run(nightmare) {
    
  var data = {
    
    'id': '2OWBTMUL',
    
    'somedata': 'blah'
    
    // More data pulled from the database goes here
    
  }
    

    
  // Create folder to hold images
    
  var procName = new Date().getTime() + '_testing_' + data.id
    
  fs.mkdirSync(path.resolve(__dirname, '../processing/', procName))
    

    
  // URL to inject into webpage so the webpage can access the data
    
  var url = `http://example.com?` +
    
    `id=${data.id}&` +
    
    `somedata=${data.somedata}`
    

    
  console.log('Starting NightmareJs')
    
  await nightmare
    
    .viewport(1920, 1080)
    
    .goto('file:///' + path.resolve(__dirname, '../templates/example.html'))
    
    .evaluate(newUrl => {
    
      // Set url and get the page ready for recording
    
      url = new URL(newUrl)
    
      initiate()
    
      start()
    
      timeline.pause()
    
    }, url)
    
    .catch(error => { console.log(error) })
    

    
  // Take 200 screenshots (8s @ 25fps)
    
  var frames = 200
    
  for (var i = 0; i < frames; i++) {
    
    console.log('Taking screenshot ' + i)
    

    
    await nightmare
    
      .screenshot(path.resolve(__dirname, '../processing/', procName, 'screen_' + i + '.png'))
    
      .evaluate(shot => { timeline.seek((8 / 200) * shot) }, i)
    
      .catch(error => { console.log(error) })
    
  }
    

    
  console.log('Done.')
    
}
    

    
// xvfb wrapper
    
function xvfb(options) {
    
  var xvfb = new Xvfb(options)
    

    
  function close() {
    
    return new Promise((resolve, reject) => {
    
      xvfb.stop(err => (err ? reject(err) : resolve()))
    
    })
    
  }
    

    
  return new Promise((resolve, reject) => {
    
    xvfb.start(err => (err ? reject(err) : resolve(close)))
    
  })
    
}
    

    
// try/catch helper
    
async function poss(promise) {
    
  try {
    
    const result = await promise
    
    return [null, result]
    
  } catch (err) {
    
    return [err, null]
    
  }
    
}


    Some environment details:

    Ubuntu 18.04.1

    Supervisor

    Node 8.12.0 (DEBUG=* set)



    The issue:
    After about 17 loops, Nightmare throws two different errors.
    In my nodejs-stderr.log file, I get this



    Taking screenshot x
    
Error: Evaluation timed out after 1000msec.  Are you calling done() or resolving your promises?


    Testing with the done() callback or promise in the evaluation didn't change anything, so I kept it simple



    In my nodejs-stdout.log file, I get this for every successful loop



    Mon, 19 Nov 2018 09:37:06 GMT nightmare:actions .screenshot()
    
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log subscribing to browser window frames
    
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log Highlighting page to trigger rendering.
    
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log unsubscribing from browser window frames
    
Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .screenshot() captured with length 1092963
    
Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .evaluate() fn on the page
    
Mon, 19 Nov 2018 09:37:07 GMT nightmare queueing action "screenshot"
    
Mon, 19 Nov 2018 09:37:07 GMT nightmare queueing action "evaluate"
    
Mon, 19 Nov 2018 09:37:07 GMT nightmare running


    And then after 17 or so loops, I get:



    Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .screenshot()
    
Mon, 19 Nov 2018 09:37:07 GMT nightmare:log subscribing to browser window frames
    
Mon, 19 Nov 2018 09:37:07 GMT nightmare:log Highlighting page to trigger rendering.
    
Tue, 20 Nov 2018 02:11:43 GMT nightmare:log crashed [{},false]
    
Mon, 19 Nov 2018 09:37:12 GMT nightmare:log FrameManager timing out after 1000 ms with no new rendered frames
    
Mon, 19 Nov 2018 09:37:12 GMT nightmare:log unsubscribing from browser window frames
    
Mon, 19 Nov 2018 09:37:12 GMT nightmare:actions .screenshot() captured with length 0
    
Mon, 19 Nov 2018 09:37:12 GMT nightmare:actions .evaluate() fn on the page
    
Mon, 19 Nov 2018 09:37:13 GMT nightmare queueing action "screenshot"
    
Mon, 19 Nov 2018 09:37:13 GMT nightmare queueing action "evaluate"
    
Mon, 19 Nov 2018 09:37:13 GMT nightmare running


    And the rest all fail, without the crashed [{},false] message.

    Removing .evaluate(shot => { timeline.seek((8 / 200) * shot) }, i) in the loop solves the issue, but I need that otherwise it's just a motionless video! I have tried separate calls (not chaining evaluate and screenshot), putting .wait(200) between stuff, but I can't figure it out or find any help on this issue.






    javascript node.js electron nightmare







    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I'm trying to setup an app I've been developing that involves recording an HTML widget (with animations) and turning it into an mp4. Locally it works great. I have Nightmare Js handling the screenshots and FFMPEG converting the screenshots into an mp4, which takes around 90s on my PC.



      I'm setting it up in a docker container through a hosting service, and cannot get past this issue. My test script at the moment looks something like this:



      const Nightmare = require('nightmare')
      
const Xvfb = require('xvfb')
      

      
module.exports = function(app) {
      
  app.get('/api/nightmare', async (req, res) => {
      
    console.log('GET request to /api/nightmare')
      

      
    try {
      
      // Start xvfb and create our nightmare object
      
      const close = await xvfb()
      
      const nightmare = Nightmare({ executionTimeout: 1000 })
      

      
      const [err, result] = await poss(run(nightmare))
      
      if (err) {
      
        // Cleanup before throwing error
      
        await nightmare.end()
      
        await close()
      
        throw err
      
      }
      

      
      // shut'er down
      
      await nightmare.end()
      
      await close()
      
      res.status(200).send('Completed')
      
    } catch (error) {
      
      console.log(error)
      
      res.status(500).send(error)
      
    }
      
  })  
      
}
      

      
async function run(nightmare) {
      
  var data = {
      
    'id': '2OWBTMUL',
      
    'somedata': 'blah'
      
    // More data pulled from the database goes here
      
  }
      

      
  // Create folder to hold images
      
  var procName = new Date().getTime() + '_testing_' + data.id
      
  fs.mkdirSync(path.resolve(__dirname, '../processing/', procName))
      

      
  // URL to inject into webpage so the webpage can access the data
      
  var url = `http://example.com?` +
      
    `id=${data.id}&` +
      
    `somedata=${data.somedata}`
      

      
  console.log('Starting NightmareJs')
      
  await nightmare
      
    .viewport(1920, 1080)
      
    .goto('file:///' + path.resolve(__dirname, '../templates/example.html'))
      
    .evaluate(newUrl => {
      
      // Set url and get the page ready for recording
      
      url = new URL(newUrl)
      
      initiate()
      
      start()
      
      timeline.pause()
      
    }, url)
      
    .catch(error => { console.log(error) })
      

      
  // Take 200 screenshots (8s @ 25fps)
      
  var frames = 200
      
  for (var i = 0; i < frames; i++) {
      
    console.log('Taking screenshot ' + i)
      

      
    await nightmare
      
      .screenshot(path.resolve(__dirname, '../processing/', procName, 'screen_' + i + '.png'))
      
      .evaluate(shot => { timeline.seek((8 / 200) * shot) }, i)
      
      .catch(error => { console.log(error) })
      
  }
      

      
  console.log('Done.')
      
}
      

      
// xvfb wrapper
      
function xvfb(options) {
      
  var xvfb = new Xvfb(options)
      

      
  function close() {
      
    return new Promise((resolve, reject) => {
      
      xvfb.stop(err => (err ? reject(err) : resolve()))
      
    })
      
  }
      

      
  return new Promise((resolve, reject) => {
      
    xvfb.start(err => (err ? reject(err) : resolve(close)))
      
  })
      
}
      

      
// try/catch helper
      
async function poss(promise) {
      
  try {
      
    const result = await promise
      
    return [null, result]
      
  } catch (err) {
      
    return [err, null]
      
  }
      
}


      Some environment details:

      Ubuntu 18.04.1

      Supervisor

      Node 8.12.0 (DEBUG=* set)



      The issue:
      After about 17 loops, Nightmare throws two different errors.
      In my nodejs-stderr.log file, I get this



      Taking screenshot x
      
Error: Evaluation timed out after 1000msec.  Are you calling done() or resolving your promises?


      Testing with the done() callback or promise in the evaluation didn't change anything, so I kept it simple



      In my nodejs-stdout.log file, I get this for every successful loop



      Mon, 19 Nov 2018 09:37:06 GMT nightmare:actions .screenshot()
      
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log subscribing to browser window frames
      
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log Highlighting page to trigger rendering.
      
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log unsubscribing from browser window frames
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .screenshot() captured with length 1092963
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .evaluate() fn on the page
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare queueing action "screenshot"
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare queueing action "evaluate"
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare running


      And then after 17 or so loops, I get:



      Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .screenshot()
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare:log subscribing to browser window frames
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare:log Highlighting page to trigger rendering.
      
Tue, 20 Nov 2018 02:11:43 GMT nightmare:log crashed [{},false]
      
Mon, 19 Nov 2018 09:37:12 GMT nightmare:log FrameManager timing out after 1000 ms with no new rendered frames
      
Mon, 19 Nov 2018 09:37:12 GMT nightmare:log unsubscribing from browser window frames
      
Mon, 19 Nov 2018 09:37:12 GMT nightmare:actions .screenshot() captured with length 0
      
Mon, 19 Nov 2018 09:37:12 GMT nightmare:actions .evaluate() fn on the page
      
Mon, 19 Nov 2018 09:37:13 GMT nightmare queueing action "screenshot"
      
Mon, 19 Nov 2018 09:37:13 GMT nightmare queueing action "evaluate"
      
Mon, 19 Nov 2018 09:37:13 GMT nightmare running


      And the rest all fail, without the crashed [{},false] message.

      Removing .evaluate(shot => { timeline.seek((8 / 200) * shot) }, i) in the loop solves the issue, but I need that otherwise it's just a motionless video! I have tried separate calls (not chaining evaluate and screenshot), putting .wait(200) between stuff, but I can't figure it out or find any help on this issue.






      javascript node.js electron nightmare







      share|improve this question















      I'm trying to setup an app I've been developing that involves recording an HTML widget (with animations) and turning it into an mp4. Locally it works great. I have Nightmare Js handling the screenshots and FFMPEG converting the screenshots into an mp4, which takes around 90s on my PC.



      I'm setting it up in a docker container through a hosting service, and cannot get past this issue. My test script at the moment looks something like this:



      const Nightmare = require('nightmare')
      
const Xvfb = require('xvfb')
      

      
module.exports = function(app) {
      
  app.get('/api/nightmare', async (req, res) => {
      
    console.log('GET request to /api/nightmare')
      

      
    try {
      
      // Start xvfb and create our nightmare object
      
      const close = await xvfb()
      
      const nightmare = Nightmare({ executionTimeout: 1000 })
      

      
      const [err, result] = await poss(run(nightmare))
      
      if (err) {
      
        // Cleanup before throwing error
      
        await nightmare.end()
      
        await close()
      
        throw err
      
      }
      

      
      // shut'er down
      
      await nightmare.end()
      
      await close()
      
      res.status(200).send('Completed')
      
    } catch (error) {
      
      console.log(error)
      
      res.status(500).send(error)
      
    }
      
  })  
      
}
      

      
async function run(nightmare) {
      
  var data = {
      
    'id': '2OWBTMUL',
      
    'somedata': 'blah'
      
    // More data pulled from the database goes here
      
  }
      

      
  // Create folder to hold images
      
  var procName = new Date().getTime() + '_testing_' + data.id
      
  fs.mkdirSync(path.resolve(__dirname, '../processing/', procName))
      

      
  // URL to inject into webpage so the webpage can access the data
      
  var url = `http://example.com?` +
      
    `id=${data.id}&` +
      
    `somedata=${data.somedata}`
      

      
  console.log('Starting NightmareJs')
      
  await nightmare
      
    .viewport(1920, 1080)
      
    .goto('file:///' + path.resolve(__dirname, '../templates/example.html'))
      
    .evaluate(newUrl => {
      
      // Set url and get the page ready for recording
      
      url = new URL(newUrl)
      
      initiate()
      
      start()
      
      timeline.pause()
      
    }, url)
      
    .catch(error => { console.log(error) })
      

      
  // Take 200 screenshots (8s @ 25fps)
      
  var frames = 200
      
  for (var i = 0; i < frames; i++) {
      
    console.log('Taking screenshot ' + i)
      

      
    await nightmare
      
      .screenshot(path.resolve(__dirname, '../processing/', procName, 'screen_' + i + '.png'))
      
      .evaluate(shot => { timeline.seek((8 / 200) * shot) }, i)
      
      .catch(error => { console.log(error) })
      
  }
      

      
  console.log('Done.')
      
}
      

      
// xvfb wrapper
      
function xvfb(options) {
      
  var xvfb = new Xvfb(options)
      

      
  function close() {
      
    return new Promise((resolve, reject) => {
      
      xvfb.stop(err => (err ? reject(err) : resolve()))
      
    })
      
  }
      

      
  return new Promise((resolve, reject) => {
      
    xvfb.start(err => (err ? reject(err) : resolve(close)))
      
  })
      
}
      

      
// try/catch helper
      
async function poss(promise) {
      
  try {
      
    const result = await promise
      
    return [null, result]
      
  } catch (err) {
      
    return [err, null]
      
  }
      
}


      Some environment details:

      Ubuntu 18.04.1

      Supervisor

      Node 8.12.0 (DEBUG=* set)



      The issue:
      After about 17 loops, Nightmare throws two different errors.
      In my nodejs-stderr.log file, I get this



      Taking screenshot x
      
Error: Evaluation timed out after 1000msec.  Are you calling done() or resolving your promises?


      Testing with the done() callback or promise in the evaluation didn't change anything, so I kept it simple



      In my nodejs-stdout.log file, I get this for every successful loop



      Mon, 19 Nov 2018 09:37:06 GMT nightmare:actions .screenshot()
      
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log subscribing to browser window frames
      
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log Highlighting page to trigger rendering.
      
Mon, 19 Nov 2018 09:37:06 GMT nightmare:log unsubscribing from browser window frames
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .screenshot() captured with length 1092963
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .evaluate() fn on the page
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare queueing action "screenshot"
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare queueing action "evaluate"
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare running


      And then after 17 or so loops, I get:



      Mon, 19 Nov 2018 09:37:07 GMT nightmare:actions .screenshot()
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare:log subscribing to browser window frames
      
Mon, 19 Nov 2018 09:37:07 GMT nightmare:log Highlighting page to trigger rendering.
      
Tue, 20 Nov 2018 02:11:43 GMT nightmare:log crashed [{},false]
      
Mon, 19 Nov 2018 09:37:12 GMT nightmare:log FrameManager timing out after 1000 ms with no new rendered frames
      
Mon, 19 Nov 2018 09:37:12 GMT nightmare:log unsubscribing from browser window frames
      
Mon, 19 Nov 2018 09:37:12 GMT nightmare:actions .screenshot() captured with length 0
      
Mon, 19 Nov 2018 09:37:12 GMT nightmare:actions .evaluate() fn on the page
      
Mon, 19 Nov 2018 09:37:13 GMT nightmare queueing action "screenshot"
      
Mon, 19 Nov 2018 09:37:13 GMT nightmare queueing action "evaluate"
      
Mon, 19 Nov 2018 09:37:13 GMT nightmare running


      And the rest all fail, without the crashed [{},false] message.

      Removing .evaluate(shot => { timeline.seek((8 / 200) * shot) }, i) in the loop solves the issue, but I need that otherwise it's just a motionless video! I have tried separate calls (not chaining evaluate and screenshot), putting .wait(200) between stuff, but I can't figure it out or find any help on this issue.






      javascript node.js electron nightmare




      javascript node.js electron nightmare






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday

























      asked 2 days ago









      Aidan

      163




      163
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          Turned out it was the shared memory being too small. I assume when the images were all loaded it exceeded the memory limit and Electron crashed. After upping the shared memory from 64MB to 128MB, the issue is solved.






          share|improve this answer





















            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',
            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
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53372889%2fnightmare-js-evaluation-timed-out-after-multiple-evaluations%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            Turned out it was the shared memory being too small. I assume when the images were all loaded it exceeded the memory limit and Electron crashed. After upping the shared memory from 64MB to 128MB, the issue is solved.






            share|improve this answer

























              up vote
              0
              down vote













              Turned out it was the shared memory being too small. I assume when the images were all loaded it exceeded the memory limit and Electron crashed. After upping the shared memory from 64MB to 128MB, the issue is solved.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                Turned out it was the shared memory being too small. I assume when the images were all loaded it exceeded the memory limit and Electron crashed. After upping the shared memory from 64MB to 128MB, the issue is solved.






                share|improve this answer












                Turned out it was the shared memory being too small. I assume when the images were all loaded it exceeded the memory limit and Electron crashed. After upping the shared memory from 64MB to 128MB, the issue is solved.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered yesterday









                Aidan

                163




                163






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53372889%2fnightmare-js-evaluation-timed-out-after-multiple-evaluations%23new-answer', 'question_page');
                    }
                    );

                    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







                    Popular posts from this blog

                    Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

                    Image
                    28 6 $begingroup$ Per the Font of Magic feature, sorcerer can use Flexible Casting to create 5th-level spell slots at level 7, even though they are not typically available until level 9. You can transform unexpended sorcery points into one spell slot as a bonus action on your turn. The Creating Spell Slots table shows the cost of creating a spell slot of [5th level is 7] If such a sorcerer levels up while still having this 5th-level spell slot, can they choose a 5th-level spell as the spell they gain upon levelling up? The Spellcasting feature states: Additionally, when you gain a level in this class, you can choose one of the sorcerer spells you know and replace it with another spell from the sorcerer spell list, which also must be of a level for which you have spell slots.
                    Read more

                    Does disintegrating a polymorphed enemy still kill it after the 2018 errata?

                    Image
                    up vote 13 down vote favorite 1 After the 2018 errata, the disintegrate spell description now reads: A creature targeted by this spell must make a Dexterity saving throw. On a failed save, the target takes 10d6 + 40 force damage. The target is disintegrated if this damage leaves it with 0 hit points. If you were to polymorph an enemy into a rat and then disintegrate it, would the enemy be disintegrated or would it just return to its original form? I know that for Druids, it’s not an instant kill anymore, but is this the case for polymorph as well? dnd-5e spells polymorph errata share | improve this question edited 18 hours ago
                    Read more

                    A Topological Invariant for $pi_3(U(n))$

                    Image
                    3 3 $begingroup$ Recently, I saw a construction of topological invariant for $pi_3(U(n))$ with $ngeq 2$ : $$ N=frac{1}{24pi^2}int_{S^3} d^3x epsilon^{ijk} Tr[(U^{-1}partial_{x_i}U)(U^{-1}partial_{x_j}U)(U^{-1}partial_{x_k}U)] , $$ where $Uin U(n)$ depends on $boldsymbol{x}=(x_1,x_2,x_3)in S^3$ , $epsilon^{ijk}$ is the Levi-Civita symbol, $i,j,k=1,2,3$ , and the duplicated indexes are summed over. It is claimed that $N$ is an integer, but why? Update 02/02/2019 I think I got an argument for $n=2$ . In this case, $U=e^{i varphi} q$ with $qin SU(2)$ . Due to the trace and the Levi-Civita symbol in $N$ , $varphi$ does not contribute to $N$ . As $Tr[q^{dagger}partial_i q]=0$ and $(q^{dagger}partial_i q)^{dagger}=-q^{dagger}partial_i q$ , $q^{dagger}partial_i q$ in geneeral has the form $q^{dagger}partia
                    Read more