FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory on 6.0.0-BETA

[bboycs]

@cnishina

Bug report

• Node Version: 6.4.1
• Protractor Version: 6.0.0-BETA
• Browser(s): Chrome
• Operating System and Version Win 10

Hi, not sure if anyone face this, but I am facing a issue where by
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Reproduction step:
execute line of code : return return browser.driver.actions().click(elementfinder).perform();
it get stuck until out of memory .

Stack trace:
<--- Last few GCs --->

[9312:00000257DABF0A10] 910793 ms: Mark-sweep 1506.8 (1647.4) -> 1506.8 (1647.4) MB, 1214.2 / 0.0 ms last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 000001D64EA25EC1
1: /* anonymous /(aka / anonymous /) [Path]\node_modules\selenium-webdriver\lib\webdriver.js:~188] [pc=000001BCFC21E451](this=0000008084802311 ,value=0000008084802351 <the_hole>,key=0000008084802351 <the_hole>)
2: / anonymous */(this=000002167DB0BE21 ,0000028D019ACC81 <String[559]: function () {\n const args = arguments;\n ...

[cnishina]

I'm not sure what the state of the actions API for chromedriver. I'm assuming it all works. The thing that looks wrong to me is you cannot mix ElementFinders and WebElements:

return browser.driver.actions().click(await elementfinder.getWebElement()).perform();

[bboycs]

I'm not sure what the state of the actions API for chromedriver. I'm assuming it all works. The thing that looks wrong to me is you cannot mix ElementFinders and WebElements:

return browser.driver.actions().click(await elementfinder.getWebElement()).perform();

Hi, It used to work in current version before BETA6 . Can i take that as software change on for BETA 6?

[cnishina]

Could you update this issue? I'm still not sure what's going on because there is not a lot of information here to figure out what you are asking. Thanks!

[jniles]

I had a very similar bug where selenium ran out of heap and crashed when trying to doubleClick(). It turns out that awaiting the getWebElement() call fixed it. Like so:

// erroneous code
const doubleClick = element => browser
    .actions()
    .doubleClick(element.getWebElement())
    .perform();

This code doesn't work and crashes with the HEAP allocation out of memory error

// working code
const doubleClick = async element => browser
    .actions()
    .doubleClick(await element.getWebElement())
    .perform();

This code works and resolves the above issue

The confusing part of this is the complete lack of error messaging to push one in the right direction. I'm pretty sure it is the same issue as @bboycs had, and this is the fix.

Maybe we can update the docs for the actions API here with an async/await example?

[OldShaterhan]

I have the same issue for such code:

`await browser.actions().
click(something).
perform();

await browser.actions().
doubleClick(somethingElse).
perform();`

something and somethingElse are set a bit earlier.