P: (Windows) Crash ( 8880582 )

I have been able to edit anouther 600 photos without a crash. My system did slow down in my second batch, but a reboot helped speed it up. I think that happened in previous versions as well so I do not believe that is new to 13.x. So the combo of the latest release and importing my catalog into a new one got me back to normal. @Rikk Flohr: Photography I think this issue can be marked as fixed. 

After a suggestion on another thread, I created a new catalog and imported my catalog into it, and that addresses the issue. I edited 257 photos without a crash and with normal performance. So, anyone who has this issue, try to create a new catalog, import your old one, and see if it goes away. I think the catalog upgrade from V12 to V13 must not have happened cleanly. I also think one of the last 2 updates contributed to the fix because my system was crashing with a new catalog on the first release of 13. I will have anouther set of photos to edit later this week or next weekend so I can try it again just to make sure. 

I just wanted to give an update to anyone else who may be seeing this issue. I am still experiencing the issue on version 13.1 and with the latest Nvidia driver 546.33.

Confirming the fact that recent Lightroom 13.02 update does not resolve the crashing issue ramdomly.

At this point my system does not have any relevance other than this just in case someone ask if my computer has the juice for Adobe products:

Device name 64NHTC6
Processor AMD Ryzen 9 5950X 16-Core Processor 4.00 GHz
Installed RAM 128 GB
System type 64-bit operating system, x64-based processor
Pen and touch Pen support

Edition Windows 11 Enterprise N
Version 23H2
Installed on ‎11/‎3/‎2022
OS build 22631.2715
Experience Windows Feature Experience Pack 1000.22677.1000.0

I just wanted to let everyone know that we may be experiencing this issue that was not fixed in today's 13.0.2. Also disabling the GPU does not help. I also updated my Bios, Chipset, and all the other hardware divers I could find just in case. 

@NYNC  I believe you are confused: 

"You (Rikk Flohr) moved it here, leading me to presume that this was the right place."

References this thread: https://community.adobe.com/t5/lightroom-classic-discussions/crash-windows/m-p/14168846#M340077. You can see your own comments about it being moved to the correct place.  It looks like you also started another thread a day later.  Those two threads were merged together.  Persons were assisting you there.

Then it appears you then posted in this unrelated thread. 

I recommend returning to your own thread and picking up the conversation there. 

I will drop a comment on that thread regarding your crash reporting, 

Rikk,

I'm left even more confused by your reply and more worried that Adobe is unaware of my problem.. While the organization of the website may be clear to you as an Adobe employee, it isn't clear to me and probably not to other users as well. Replies from you as an Adobe rep are interspersed with comments from other customers. When a post from you in the forum says that "we've reviewed the email address you use with this forum and find no crash reports", that reply is not plainly linked to any individual. It's impossible from my point of view to know whether you are addressing me or the originator of the first post, which is now many screens away in this long thread. The exception is when the reply arrives in an email direct to me, as did your reply today to my latest post in which you suggest that I'm in the wrong thread. How it got here is as follows:  Originally, I inadvertently posted my inquiry in a Mac forum, not realizing that problems were separated by OS. You (Rikk Flohr) moved it here, leading me to presume that this was the right place. When I repeated the post and added some additional information, you admonished me not to post the same thing twice. 

Since this is a problem with GPU acceleration failure in one feature, not a full crash with data loss, it indeed sounds like I need to be on a completely different thread. I doubt crash reports were generated absent a full crash (I use only the one email address). BTW, when I click the link to which you directed me saying that a bug is under investigation, I only get a Page Not Found Error 404 message, so I can't get clarification about what is being investigated.

If this needs to be in a new thread, can you assist me in starting it? 

I'll follow your admonition and refrain from reposting further details until we're in the right place. Sorry to be so long-winded. I do hope you can help get the post in the right place and the problem fixed. 

Thanks.

@NYNC 

I am unsure what the question is, but my post is self-explanatory. 

The original post on this thread is marked Bug: Investigating.  That means a bug has been filed and is under investigation. See the original post: https://community.adobe.com/t5/lightroom-classic-bugs/p-windows-crash-8880582/ 

Further, see this note from me on the Pinned Post at the top of every page in this thread: 

"I've finally located one of your crash reports and it matches to an existing bug in our system. I am connecting this post to that bug. Thank you for your report." 

The document https://helpx.adobe.com/lightroom-classic/kb/fixed-issues.html  lists the bug fixes. This bug isn't on it. 

Distilled to its essence: #1 on your list. 

Additional information will be made available - when it is available. 

Now, to you specifically: 

I find no crash reports in our system from your email address. That leads me to believe that this may not even be the same as your issue. Did you post on this thread, or were you merged in by one of the Admins? Sometimes, people read a thread and think, "yeah, this is EXACTLY my problem." they reply post, wait, and then when the fix comes, they complain loudly about it not really being fixed. 

I suspect you are on an unrelated thread unless you have crash information submitted under a different email than the one you use in this forum. Is that possible?

Rikk, thanks for your quick reply but may I ask for clarification? What exactly does your comment that the GPU acceleration bug is not on the "list" of fixes remedied in LR Classic 13.0.2 mean? (1) It is a bug known to Adobe, they are working on it, but they definitely haven't fixed it yet. Be patient, (2) It is a bug known to Adobe, but they have no plans to fix it. Buy a new graphics card, (3) Adobe's lists of bugs fixed by an update are never comprehensive, so the update might actually have fixed it but you can't confirm it. Give it a try at your own risk,  (4) Adobe hasn't fixed the bug because they are not even aware of it. If the latter, what do users have to do to document it for Adobe and move it up on the priority list? I don't have crash reports to send because LR doesn't crash. It just shows a blank screen when I try to magnify the view on monitor 2 in Develop mode. Thanks.