Node.js: Server-side JavaScript has stopped working.

[#1]

Hello Everyone,

After the last Adobe Creative Cloud update. I receive this error every second that takes me out of the program I am currently in. (Indesign, Premiere, Aftereffects, Photoshop). I am currently at a stand still, where a similar problem happened less than a month ago with Error: "Evented I/O for V8 JavaScript has stopped working" .

How many problems can you cause with every update Adobe? Can you fix these before updating and how do I fix this one now since I literally slowed to a snails pace with this issue.

Thanks.

[#2]

Hello Everyone,

After the last Adobe Creative Cloud update. I receive this error every second that takes me out of the program I am currently in. (Indesign, Premiere, Aftereffects, Photoshop). I am currently at a stand still, where a similar problem happened less than a month ago with Error: "Evented I/O for V8 JavaScript has stopped working" .

How many problems can you cause with every update Adobe? Can you fix these before updating and how do I fix this one now since I literally slowed to a snails pace with this issue.

Thanks.

[#3]

I have the exact same issue.... this is absolutely ridiculous!

[#4]

WORKAROUND: Backup and delete C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCLibrary\libs\node.exe

This is not recommended but will free you to go through this stupid error all the time

[#5]

Other than the obvious workaround benefit, what gets affected by deleting node.exe?

[#6]

I couldn't tell you, for now didn't notice any difference but it is certain that even before deleting it the node.exe wasn't being any helpful because of this error

[#7]

You my son are a hero.

[#8]

Yes, so far the only true fix! Kudos to you and thank you!

[#9]

Windows 10 is apparently immune, Windows 7 SP1 is affected and I don't know about Windows 8

[#10]

Same issue here but deleting node.exe didn't resolve the issue (though node.exe is what is referenced in the details of the error).  Any other thoughts out there?  I tried stopping the creative cloud app from starting at login but that didn't help.

[#11]

I have deleted the node.exe and the error comes up less often, but still comes up.

[#12]

I got rid of the evented I/O problem and now this is destroying my processing time. Why is it occuring? why does adobe not

fix it when they see re all frustrated? Helen

[#13]

Perhaps Adobe applications have recreated the node.exe, try to check if it is still there, because without node.exe this error should no longer appear, try also check Windows Updade if you have all the updates installed.

[#14]

I checked and there wasn’t a new instance of node.exe after I deleted it but somehow that error still shows up.

[#15]

I still get node.exe to come up Russellk. This just occurs less often after deleting the file. So its a bandage, not a fix.

[#16]

I am able to work right through the error message but it is annoying. Still using Windows7 and will as long as possible.