Polygonal Lasso Tool Problems

[Sharprock86]

Hi everyone,

Using the Polygonal Lasso Tool, and this one only, my Photoshop often freezes and stops working. I don't know if this could be ascribed to a low RAM problem, because many other operations more demanding don't cause this issue. Is there anyone else who had the same problem and maybe solved it?

Thank you very much,

Simone

[Thendral barathi]

Please give specification of your system. Then only some one helps to you.

[Sharprock86]

You're right, I forgot...

System info:

OS:               Windows 10 enterprise x64

CPU:             Intel(R) Core(TM) i7-4771 CPU  -    3,50GHz

RAM:           16 GB

Video:           GeForce GTX 760

[Thendral barathi · Accepted solution]

Hey system wise there is no problem. Kindly remove your RAM and fix it after cleaned. 

Try resetting your Photoshop prefrences. 

General Tab in Photoshop preferences.

If you can't open the application to do that use this technique:

Close Photoshop, Double click on Adobe Photoshop icon to launch it, QUICKLY hold down Ctrl+Alt+Shift,
When a dialog appears, ask you “Delete Photoshop Preference Files?” Click Yes.

If that doesn't help, come back here for more suggestions.

[Sharprock86]

Ok, I'm trying that way and see if it works.

Thank you very much, sbdhasan

[Capt Wilki]

Hi

Did this work for you?

Ive tried it and its no different

Regards Brian

[Sharprock86]

Hi Brian,

sorry for the incredible delay.

Indeed I solved the problem with the updates; with the last one, it should clean many conflicts and errors. 

Have a nice day.

Simone

[jlnas]

Resetting preferences did not work for me. I have one layer, feather se t to 0, yet the polgon lasso tool almost always gives me the 0 pixels selected or less than 40 % selected. It also closes before I finish my polygon, and then opens at a new start point seemingly at some random point.

[자룡조8879156]

I have the same problem.
I upgraded RAM but the problem still comes out.
I don't think Adobe will fix it.

[Sharprock86]

Hi,

it is not a problem of RAM nor CPU, I think it is some kind of conflict with Win. Infact it was solved by the following update and whilst it created other conflicts with other tools the last one  (v.21.2.1) seems to have solved them all (so far).