Participant

解決済み

Error: "Evented I/O for V8 JavaScript has stopped working"

Forum|Forum|10 years ago
November 24, 2015
返信数 34.
39439 ビュー

Has anyone had this issue? Does anyone know what is causing the error?

Creative Cloud

このトピックへの返信は締め切られました。

解決に役立った回答 peterk26211024

This has been going on for the past couple days now. There are a number of forums posts about this with no fix from Adobe yet.

Re: Indesign: evented I/O for v8 javascript has stopped working

I've seen this when indesign or photoshop is open and problem started when updating the Adobe Creative Cloud app. This is affecting hundreds of users spread across multiple companies I manage.

I've managed to stop the error by doing the following

renamed node.exe to node.bak in the following locations:

C:\Program Files\Adobe\Adobe Photoshop CC 2015\
C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCLibrary\libs\
C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCXProcess\libs\

Waiting for appropriate fix from Adobe as this is a wide-spread issue.

svg44

Participant

For the fact that the problem appeared in Windows 7 Pro 64bit after installing my subscription there I did some search and found this manual, which I tried and which worked for me.

Already the second time in my short discription period Adobe didnt do the job well and in time....

Try this:

Evented I/O for V8 JavaScript stopped working : creativecloud

paulh1500496

Participant

I am still getting this issue despite following the multitude of suggestions in the preceding posts.

The issue is linked to node.exe in the following location: "Program Files (x86)/Adobe/Adobe Creative Cloud/CCXProcess/libs/node.exe"

There is another instance of node.exe in a different folder however disabling the one above has stopped all instances of the annoying pop up. Disabled by renaming to "node.bak.exe".

Windows 7 64 bit

Error log detail:

Fault bucket , type 0

Event Name: CLR20r3

Response: Not available

Cab Id: 0

Problem signature:

P1: node.exe

P2: 0.10.40.0

P3: 559ee7b9

P4: ProxyResolverWin7

P5: 0.0.0.0

P6: 565605d1

P7: 70

P8: 224

P9: System.IO.FileNotFoundException

P10:

Attached files:

C:\Users\Paul\AppData\Local\Temp\WER6FF2.tmp.WERInternalMetadata.xml

These files may be available here:

C:\Users\Paul\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_node.exe_3e94a2344dec5a6c74871ee1433aa34c165612_10fa75ac

Analysis symbol:

Rechecking for solution: 0

Report Id: add4d8d6-a9aa-11e5-bcc6-bc5ff43ad8f4

Report Status: 1

paulh1500496

Participant

Downloading the latest 32 bit version from Download | Node.js and copying it on top of the old version worked a treat. All working and no further issues.

L

llull

Participant

I'm using this solution for now. I renamed (Admin Rename) node.exe to node__.exe in all 3 places, restarted Photoshop CC 2015, and am currently not receiving the error.

What a fiasco.

L

LOR2013

Participant

hi

have been getting this problem since last update. but found solution. open CC and sign in - go into preferences then Creative Cloud - Apps tab and untick 'Show OS notifications' Then do the same in the Files tab, then Fonts and Behance tabs. haven't seen message since i did this.

Drt_Harrie

Participating Frequently

When you have the latest version of the creative cloud desktop, the disabled of notifications shouldn't be needed.

are you sure you are running with the latest version of the Desktop app?

3.4.1.181 was the patch that resolved the error.

Jeffrey_A_Wright

Community Manager

Martin15 as Drt.Harrie has posted this should be resolved with the current version. Can you please contact our support team directly at Contact Customer Care. If you can please update this discussion with your case number I would like to review the interaction to determine why you continue to receive the Evented I/O for V8 Javascript error.

monana

Participant

I called Adobe Support. They had discovered a bug in the latest update and there is now a fix for this.

If downloading the fix (update) does now work, then uninstall that application and start from scratch with a download of the application that fails (Full package or individual)

I did this yesterday 2015-12-01 and does not have the issue anymore

Regards, Mona

A

Anonymous

Still the same.

After starting Creative Cloud, the CCProcess almost killed my CPU.

I'm using OS X 10.11.1.

M

MOKI65

Participant

Hope for italian update soon...same problem here

Å