Photoshop CC 2018 Crashing after pen tool use

Report · Jan 24, 2018

I've been working on a project all day that requires heavy use of the pen tool and shapes made from the pen tool. After I make a few shapes with the pen tool my program crashes.. I'm talking about alllllllll day long. I've uninstalled and reinstalled but the problem still persists. I have a copy of the crash log, but it is quiet long.. here is the beginning, if more of the report is needed please let me know.

<?xml version="1.0"?>

<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">

Thanks for any suggestions or help you can offer!

Report · Jan 26, 2018

jbm007 psteamscribe

I installed 19.1 on my recently formatted ASUS ROG laptop (completely different machine) and am getting a 100% (10/10) repo on the circle method I posted above

Windows event log:

Log Name: Application

Source: ESENT

Date: 1/26/2018 8:39:55 PM

Event ID: 916

Task Category: General

Level: Information

Keywords: Classic

User: N/A

Computer: DESKTOP-P0BIVLT

Description:

DllHost (9116,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP-P0BIVLT</Computer>

</System>

<Data>DllHost</Data>

<Data>

</Data>

<Data>EseDiskFlushConsistency</Data>

<Data>ESENT</Data>

</EventData>

</Event>

Here is the adobe crash log:

<?xml version="1.0"?>

<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">

<stackStatement index="0" address="0x00007FF716486E83" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="1" address="0x00007FF71648569B" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="2" address="0x00007FF71649E150" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="3" address="0x00007FF716499940" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="4" address="0x00007FF71649E0AB" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="5" address="0x00007FF715A9A60C" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="6" address="0x00007FF715A9A694" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="7" address="0x00007FF715408DAC" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="8" address="0x00007FF71540998B" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="9" address="0x00007FF715409049" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="10" address="0x00007FF716416154" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="11" address="0x00007FF716419514" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

</thread>

</backtrace>

</registerSet>

</binaryImageSet>

Mini

</dumpType>

</crash>

</crashreport>

Report · Jan 25, 2018

I'm on a laptop with Windows 7 and 16GB memory. I'm not using a Wacom tablet or anything.

In the file i sent, i just used the pen tool to draw out the lines between the boxes and then stroke the line (right click->Stroke path->Brush).

Using the pen tool to make a selection generates the same result. However, replicating this error isn't the easiest thing. Sometimes it crashes after just a few lines and sometimes i can draw paths for a minute before it crashes. I just open a new 1200x800px document and draw paths on the background layer. It crashes sooner or later every time.

Report · Jan 25, 2018

1. Working with the old pen tool

2. I had a crash after making a 500x500 pixel circle, and made 2 pen shapes on it. Also, had it crash when I was going crazy with the pen tool seeing if that was in fact what was causing my problem (prolly 20 shapes before it crashed). The project I was working on when it crashed, I had like 2 groups with 2 shapes in each group nothing crazy.

3. I was opening a New project just to test and was getting constant crashes on New projects. Didn't want to start working on a large project only to get frustrated.

Report · Feb 09, 2018

Pen, crashes after first or second path (e.g. immediately) ... have the newest CC downloaded from the cloud in December.

Report · Jan 29, 2018

This started happening to me this morning. Running Windows 10, i7, 12 GB RAM. I've used Photoshop (mostly in conjunction with Lightroom) for years but recently bought the 2018 Classroom in a Book to "up my game". As soon as I got to the chapter on vector shapes and paths I started getting crashes -- about a dozen so far this morning. Sometimes I get the Adobe Crash Report screen and sometimes the Windows crash screen (closing program, searching for solutions, etc....). I've restarted the computer, turned GPU acceleration off and on with no change.

The file I'm using is 08Practice_Start.psd, but I get the same problem with a new, blank document.

Tried both the Pen tool and the Curvature Pen tool, both cause crashes. I'm going to see what happens on my laptop next. I can't recall it it's been updated to 19.1 or not.

Also: tried with both mouse and graphics tablet (Huion) with same results.

Report · Jan 29, 2018

I have the same issue with latest software... crashes every time i try to use the magnetic lasso tool.... among other glitches with the latest version of Photoshop... ended up downgrading to CC2017....

Report · Jan 29, 2018

Folks:

Thank you, thank you, thank you for all your crash logs. We're still trying to reproduce this crash in house, and several of our engineers are working on diagnosing the problem.

Thanks for your patience as we try to sort this out.

Eric Floch

Photoshop Quality Engineer

Report · Jan 29, 2018

Eric

Check my comments to your post.

Jim

Report · Jan 29, 2018

I just completed an online support session. We installed 2017 version and the problem went away. I just turned on my (seldom used) laptop. It is on version 19 and does NOT have the issue. I'm installing 19.1 right now and will see if it has the crash issue. The rep I worked with in the online session said it is a ”graphics problem.” Note: I got crashes both with and without GPU acceleration turned on.

Report · Jan 29, 2018

Just updated my laptop from 19 to 19.1 and now the Pen tool crashes. Note: my laptop has not been turned on for nine days, so it does NOT have any recent Microsoft or Intel patches. Laptop is Windows 7 and desktop is Windows 10, both have the issue.

Report · Jan 29, 2018

OK so its random, it affects different applications, but it all relates

back to this beta app that a Microsoft patch appears to have installed.

I have 19.1 on and it does not crash using any tools.

I don,t know when windows did a update, and which is causing the problems.

Not all machines are effect, the complaints on the user forum were all

from windows 10 users who had this ESENT beta software install.

Report · Jan 29, 2018

This problem is a windows creator issue.

This issue is running rampart on a lot of games forums.

From one of the forums. Adobe is just another app that is having issues.

Not all games are effected.

It looks like memory allocation issues.

0

Am being significantly impacted by PC activity that is throwing this message. There is some sort of problem that is throwing this message, but I have no idea if some aspect of EseDiskFlushConsistency or ESENT (whatever THEY are) is the culprit or if that is just a message that is a symptom of some other issue, such as malware (I run Norton).

I have two accounts on a ASROCK motherboard running an AMD processor with 8GB. The normal (non-admin) MS account that I normally use seems to be working without difficulty. The local admin account (that I rarely use) is crippled by problems that has thrown thousands of "Information events" (62,506 [the max it will hold?]) in one 4 hour period this evening, but I have been fooling with this for most of the afternoon, so I suspect there were thousands more that were discarded..

I wanted to track down a problem with MS Outlook (Office 365) "restarting" arbitrarily several times a day (especially when editing a draft). Following a suggestion, I signed out and logged into the admin local account.

It was unusable. Slow as Christmas.

Wanted to start sysconfig, but help box took 10 seconds to type each letter.
Minutes to load a page in Edge.
Task manager showed "Host Process for Windows Tasks", an independent process runningtaskhostw.exe, driving disk activity at 25-30%. Went on and on, almost without pause.
Used Task Manager, the standalone Windows executable "Process Explorer", Event Viewer, and Resource Monitor to gather local performance data about the process, including vast numbers of these EseDiskFlushConsistency messages. Logged out and looked the message up on browser. Tried rebooting, shutting down non-Windows services I don't need ("clean boot"), switching back and forth between the admin and non-admin accounts.
Finally, in Process Explorer, I killed the svchost.exe process tree that included taskhostw and UMont64.exe. Momentary relief.
Then, after a little while, dllhost.exe ("COM Surrogate") started doing almost the same thing (high disk activity, same message except that it cites dllhost.exe). It would occasionally pause for a while (15-20 seconds or so) then start again. I killed the first one I found using Process Explorer, but another one jumped in. I killed that one too.
Meanwhile, the Edge browser was running extremely slowly.
Logged out and back in again. taskhostw started acting up again and I killed it with PE again, this time only killing taskhostw, not the UMont64.exe process that was in the same tree. Momentary relief. I ended up killing UMont64.exe, too. Momentary relief.
Starting Edge or Settings kicked off COM Surrogate/dllhost.exe with high disk activity.
Closed both Edge & Settings, but COM Surrogate just keep running at high disk activity. I ran out of patience; it might have settled down on its own.
I checked for system file errors with DISM and sfc. Found nothing.
Once the taskhostw and dllhost tasks are killed the disk activity settles down, but the browser on the admin account is still too slow to be usable. I have seen taskhostw jump back in but not start driving the disk activity like before. I have also seen EseDiskFlushConsistency event messages that cite svchost and RuntimeBroker.
I am confident that going back into the admin account will just start taskhostw on a tear again.
I note that in the normal (non-admin) account COM Surrogate fires briefly when doing browser and settings activity but it then settles down quickly; and it never gets to the 25-30% of disk that it showed in the admin account.

I hope this (excessively long) narrative will offer a clue to someone who can fix this kind of thing.

Update the next day: After I posted this, I noticed last night, while logged into in the normal (non-admin) account, that I was still getting these notices, but not nearly as frequently; Task manager did not show anything unusual and performance did not seem excessive. This morning, after waking up the PC in the normal account, in about 30 minutes I received another 25 of these messages, citingsvchost a couple of times, mostly RuntimeBroker, and once by SettingSyncHost (right as the computer woke up). Now, 10 minutes later, they seem to have stopped being thrown (of course, all I have done in those 10 minutes is edit this post and look at Event viewer). I'm going to

Report · Jan 29, 2018

I ran into this same problem and wrestled with it and wasted quite a few hours tonight

The pen tool and line tool both seemed to cause a crash consistenty, the pen tool always crashed after stroking a path with the brush selected. the canvas was 5000 w x 3000 h and 300 Dpi and I was zoomed in somewhat. I probably sent in about 8 crash reports.

I have a reasonably powerful computer, win10, 4core 4.1 ghz cpu, gtx 960 4gb, 16gb ram and I was running ps off an ssd.

I tried fiddling with photoshop settings and tried everything on the optimization page, tried plain old reset pc, upgraded graphics card drivers, reset preferences, nothing would make it stop, I think something between windows and the most recent update is making things unstable.

I have since gone back to version 19.0 and things seem stable so far so that seems to be a solid workaround for now

Report · Jan 30, 2018

Same problem here. I guess I will be using an old version for a while.

Report · Jan 30, 2018

For what it's worth, I'm having the same problem and it came up about the same time as everyone else. Occurs when I use the pen tool AND when I try to manipulate the nodes on a line with the Direct Selection Tool.

Also, Photoshop 19.1 is running slower that normal. For example, when I try to resize an object it hangs for a few seconds and when I hit < CTRL + 0 > to "fit to screen," the image disappears for a few seconds, then comes back fitted to screen.

Crash report below. Windows 10.

<?xml version="1.0"?>

<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">

<stackStatement index="2" address="0x00007FF796ABF5BD" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="3" address="0x00007FF79793F67B" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="4" address="0x00007FF79793F7D0" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="5" address="0x00007FF797941D6B" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="6" address="0x00007FF79793EE37" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="7" address="0x00007FF797BC40C9" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="8" address="0x00007FF797B4936B" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="9" address="0x00007FF7973A565C" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="10" address="0x00007FF7973B0846" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="11" address="0x00007FF79828AB6B" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="12" address="0x00007FF798283C32" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="13" address="0x00007FF79830C220" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="14" address="0x00007FF79830C2C0" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="15" address="0x00007FF79832DF06" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="16" address="0x00007FF798351076" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="17" address="0x00007FF796C6A071" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

<stackStatement index="18" address="0x00007FF79832FB58" symbolname="boost::serialization::singleton<boost::archive::detail::extra_detail::map<boost::archive::xml_oarchive> >::get_instance"/>

</thread>

</backtrace>

</registerSet>

</binaryImageSet>

Mini

</dumpType>

</crash>

</crashreport>

Report · Jan 30, 2018

Folks:

So I was finally able to reproduce the crash in house, via Joe's steps above, with ONE additional step. These crashes seem to be at least tangentially related to another bug we've been working on -- which one of the posters actually mentioned above -- a crash with the magnetic lasso tool. The operative factor with both bugs seems to be having Precise Cursor turned ON.

So let me ask you all... Are you all working with Precise Cursor turned ON -- either via Preferences (Prefs > Cursors > Precise setting for Painting and/or Other Cursors) or by simply keeping Caps Lock ON -- so the cursor appears as a crosshair?

This was the factor that got me crashing. Shame on me for not thinking of it earlier, but there you go. I would assume, given that many of you are working with paths and shapes on a very regular basis, that it's probably the case for all of you that you have this turned on.

If so, good news... We know what the problem is, we have a solid fix that should be coming out in a future release of Photoshop, and there's an easy workaround -- simply turn Precise Cursor OFF -- either via Preferences or by setting Caps Lock to OFF. If Precise Cursor is essential to your workflow, you should certainly go back to/continue to use Photoshop 19.0 for the time being (to go back to a previous version, please see the steps I posted in the thread above).

If you're NOT using Precise Cursor, please speak up and let me know on this thread. If there's something else going on here, we definitely want to figure out what's going on. But for me, that was absolutely the trigger cause of the crashes I was able to reproduce. WIthout Precise Cursor/Caps Lock ON, I could work all day with paths and shapes without crashing.

Thanks so much for all of your help. Please do let me know if you turn off Precise Cursor and are still crashing.

Eric Floch

Photoshop Quality Engineer

Report · Jan 30, 2018

Neither one of those selection options effects my system .

No crashes, and I have tried every tool in PS

There has to be some other correlation else causing it.

Windows Creator x64 OS

Report · Jan 30, 2018

Thanks so much for your reply. So, if I'm understanding your post, you're not seeing any crashes? Is that correct? If not, that's great.

Just in terms of troubleshooting this... There are actually two reasons I don't think any of this has to do with a particular version of Windows, but rather with US...

1. People on this thread have been seeing the problem on Win 7 as well as Win 10.

2. They didn't start seeing the problem until they installed Photoshop 19.1. And unfortunately, in some cases, it seems the crashing started immediately with our update. And our update almost certainly wasn't absolutely coincident with a Windows system update in all these cases.

If my logic is incorrect, we can certainly discuss. Note that I'm not arguing that Windows isn't ALSO having a problem causing apps to crash/malfunction. I just believe that our investigation indicates that these particular crashes are OUR problem (which we're going to fix).

Thanks so much.

Eric Floch

Photoshop Quality Engineering

Report · Jan 30, 2018

Just to restate: After having the problem on my Windows 10 desktop with version 19.1 I checked my laptop. It was still on 19 and did not have the problem. Also, It had not been turned on in nine days, so did NOT have any recent Windows updates. I updated the laptop to 19.1 and immediately experienced crashes when trying to use the Pen tool.

I just rolled the laptop back to 19 and it is OK again (no crashes).

Report · Feb 01, 2018

I agree with you!

Report · Jan 30, 2018

Sorry to report that I do NOT have precise cursor turned on and I get the crash immediately after creating a path. (Windows 10 desktop with version 19.1.) I can click once with the Pen tool, then click a second time, then hit <Enter> and CRASH.

I just rolled my Windows 7 laptop back to 19 and it's OK again. On my Windows 10 desktop I still have 19.1 installed as well as the 2017 version as a backup option.

Report · Jan 30, 2018

Yeah, what jbm007 said.

I never changed those settings. Normal brush tip and standard. Glad you're able to reproduce it though!

Does just having the polygonal or magnetic lasso tool in the toolbox selected cause a crash? That's one step you could have done to start getting consistent crashes?

Report · Jan 30, 2018

Yes, the Magnetic Lasso tool crash was one we knew about, and that's what we have the fix for. It seems to also address the Pen tool crashes -- I can get the crashes with Joe's steps above so long as I have Caps Lock ON, but NOT after installing the fix we have for Magnetic Lasso.

Another permutation (seemingly) of the same issue was that I was able to crash Photoshop with the Freeform Pen tool and the Magnetic option checked ON. This crash is also gone with the fix we have.

But everything I'm talking about had to do with turning ON Caps Lock to activate the Precise Cursor.

Hmmm, I was feeling so sure we had cracked it. Please keep chiming in if you're seeing crashes without Precise Cursor. I'll keep poking around. Thanks.

Eric Floch

Photoshop Quality Engineer

Report · Jan 30, 2018

Okay, we've got it now!

I have a reproducible case for what you guys are seeing, separate from the Precise Cursor issues with Magnetic Lasso and the magnetic option with Freeform Pen tool.

So sorry it took so long, but we're on it. Our developers are looking at it as we speak.

Thanks for all your persistence and your excellent information. I'll let you all know as soon as I know more.

Eric Floch

Photoshop Quality Engineer

Report · Jan 31, 2018

Getting this crash *every time* I use the Direct Selection tool on any new or existing shape. On Win 10 64. 19.1.0 CC

* Tap "a" key for Direct Selection tool

* select a point and move it around

* drag a selection window (I see a display refresh issue with the selection marquee)

* Photoshop crashes every time

* sadness ensues

Note: I tried the compatibility mode and checked for precise cursor. Neither seemed to matter.

Adobe Community

Photoshop CC 2018 Crashing after pen tool use

1 Correct answer

Explore related tutorials & articles