This began in the rollout of Pro 2.4. Then it was raster layers that if you tried to un-check them during editing, it would cause the Pro project to crash. So now that problem has migrated to feature layers. Created a simple line feature layer with COGO enabled. Seemed to work fine for a couple days and now if I want to edit a different layer, and don't want to accidently edit my COGO layer, if I uncheck the COGO layer, Pro project crashes....
I'm sorry to hear that Pro is crashing for you. I'm trying to reproduce the scenario. Here is what I've tried so far:
I seem to be missing something.
Please let me know,
I didn’t capture the error message, but it happened again when I was trying to edit “ROADCENTERLINE_WORK” in the attached mmpk. I was simply unchecking (or clearing?) the other layers in this project from being editable when Pro crashed…
Kory Kramer also responded, so if you know him you can share this with him.
Good luck, seems to be a problem…
Thanks for the data, Pete. I'm testing in 2.4.1, and I can't reproduce either (like Thomas below). Were you using 2.4.1 when it crashed for you?
I just spoke with Kory, but he said was in touch with you regarding a different (albeit similar) crash issue that you reported here - https://community.esri.com/thread/236005-arcpro-240-editing-issue-with-sid-imagery-in-a-project
That issue was fixed in 2.4.1, so I would like to confirm the version you are using.
Also, after a crash, an error report file is generated in C:\Users\yourusername\AppData\Local\ESRI\ErrorReports\ - Are you saying there is no error report in that location for you? If there are, please send the relevant one to me at firstname.lastname@example.org
I agree with Thomas that Technical Support is a good resource for reporting issues like this - since sometimes the steps are very workflow and/or data specific. Here is contact info for Technical Support - https://support.esri.com/en/contact-tech-support
Yes. I tend to be pretty quick on the mouse when checking/unchecking layers. Try to be sloppy with mouse and see if that reproduces anything. And, just a quick question, what happens to the data that I send up to geonet?
I'll have to assume when you say yes, you mean you are using 2.4.1 and Yes, there are no error reports in that location. If so, that's very odd.
I'll try your suggestion of clicking sloppily
Regarding the data - perhaps you can remove it from your post. I'm going to attach a test file to this comment and I'll see if I can delete it right now