Torstein Posted December 16, 2023 Share Posted December 16, 2023 Two times I have experienced 2.3 suddenly quit without giving any warning. That has actually has cost me and hour work or so... Everything is fine with my PC and this is the only application that has done this to me. I'm using a PC with Windows 11, Ryzen 5700G, RTX 2060 and 32GB RAM Quote Link to comment Share on other sites More sharing options...
Staff DWright Posted December 16, 2023 Staff Share Posted December 16, 2023 Can you please provide more information on your workflow when the crash report and can you please check the following location to see if a crash report was generated for the time of the crash and if there is one please post the dmp file %UserProfile%\.affinity\Photo\2.0\CrashReports\reports\ Quote Link to comment Share on other sites More sharing options...
Torstein Posted December 17, 2023 Author Share Posted December 17, 2023 20 hours ago, DWright said: Can you please provide more information on your workflow when the crash report and can you please check the following location to see if a crash report was generated for the time of the crash and if there is one please post the dmp file %UserProfile%\.affinity\Photo\2.0\CrashReports\reports\ Sorry, there was no crash report. I dont think I can give a very good description of my workflow.... I was working on a jpg file exported from DxO PhotoLab. I was doing quite a bit with the photo. Duplicating the layer 3 times and masking two of the layers. On one of the layers, I also had two masks. Adding several effects like blur, high pass filter etc. etc. Anyway, it's not a masterpiece, but I guess I can add the new version of the file here, a somewhat simpler version not quite finished... Vintermåker.afphoto Quote Link to comment Share on other sites More sharing options...
Captain Haddock Posted December 27, 2023 Share Posted December 27, 2023 On 12/16/2023 at 8:18 AM, Torstein said: Two times I have experienced 2.3 suddenly quit without giving any warning. That has actually has cost me and hour work or so... Everything is fine with my PC and this is the only application that has done this to me. I'm using a PC with Windows 11, Ryzen 5700G, RTX 2060 and 32GB RAM I've had the same problem. Perhaps a Microsoft update messing with Photo? 79b437eb-f238-4fd0-87ae-8a5644c4d623.dmp 38919167-0c1e-4282-b298-a61cb9c82bd6.dmp Quote Link to comment Share on other sites More sharing options...
v_kyr Posted December 27, 2023 Share Posted December 27, 2023 6 minutes ago, Captain Haddock said: I've had the same problem. Perhaps a Microsoft update messing with Photo? Looks more to be an OpenCL problem in your case here, aka GPU driver and OpenCL libary related ... Quote Operating system: Windows NT 10.0.22621 2506 CPU: amd64 family 6 model 154 stepping 3 20 CPUs Crash reason: EXCEPTION_ACCESS_VIOLATION_READ Crash address: 0xffffffffffffffff ** ** Non-canonical address detected: 0xeffffffffffffffc Crashing instruction: `mov r10d, dword [rdx + 0x14]` Memory accessed by instruction: 0. Address: 0xeffffffffffffffc Size: 4 Process uptime: 60 seconds Thread 54 (crashed) 0 opencl-clang64.dll + 0x1d0f77b rax = 0xf000000000000000 rdx = 0xefffffffffffffe8 rcx = 0x000001bc4daf7701 rbx = 0x000001bc4daf76e1 rsi = 0x000001bca508d678 rdi = 0x0000000000000000 rbp = 0x0000000000000000 rsp = 0x0000002ffeffda20 r8 = 0x000001bca508d658 r9 = 0x0000000000000001 r10 = 0x000000000000001c r11 = 0x0000002ffeffd990 r12 = 0x000001bc8298fb80 r13 = 0x000001bc3e1a1560 r14 = 0x000001bc39ae8c00 r15 = 0x0000000000000000 rip = 0x00007ffc34a0f77b Found by: given as instruction pointer in context 1 opencl-clang64.dll + 0x1cae1ff rsp = 0x0000002ffeffda30 rip = 0x00007ffc349ae200 Found by: stack scanning 2 opencl-clang64.dll + 0x250ee1f rsp = 0x0000002ffeffda40 rip = 0x00007ffc3520ee20 Found by: stack scanning 3 opencl-clang64.dll + 0x1cac534 rsp = 0x0000002ffeffda60 rip = 0x00007ffc349ac535 Found by: stack scanning 4 opencl-clang64.dll + 0x1cae3a3 rsp = 0x0000002ffeffdaa0 rip = 0x00007ffc349ae3a4 Found by: stack scanning 5 opencl-clang64.dll + 0x1a964fa rsp = 0x0000002ffeffdad0 rip = 0x00007ffc347964fb Found by: stack scanning 6 opencl-clang64.dll + 0x1c9d3e4 rsp = 0x0000002ffeffdb10 rip = 0x00007ffc3499d3e5 Found by: stack scanning 7 opencl-clang64.dll + 0x1c95a0f rsp = 0x0000002ffeffdb20 rip = 0x00007ffc34995a10 Found by: stack scanning 8 opencl-clang64.dll + 0x4885087 rsp = 0x0000002ffeffdb58 rip = 0x00007ffc37585088 Found by: stack scanning 9 opencl-clang64.dll + 0x1ca2f26 rsp = 0x0000002ffeffdbb0 rip = 0x00007ffc349a2f27 Found by: stack scanning 10 opencl-clang64.dll + 0x250eeaf rsp = 0x0000002ffeffdbe0 rip = 0x00007ffc3520eeb0 Found by: stack scanning 11 opencl-clang64.dll + 0x248009e rsp = 0x0000002ffeffdc10 rip = 0x00007ffc3518009f Found by: stack scanning 12 opencl-clang64.dll + 0x3cfa06f rsp = 0x0000002ffeffdc78 rip = 0x00007ffc369fa070 Found by: stack scanning 13 opencl-clang64.dll + 0x1ca207f rsp = 0x0000002ffeffdcf0 rip = 0x00007ffc349a2080 Found by: stack scanning 14 opencl-clang64.dll + 0x1a4f127 rsp = 0x0000002ffeffdd40 rip = 0x00007ffc3474f128 Found by: stack scanning 15 opencl-clang64.dll + 0x3cfa03f rsp = 0x0000002ffeffdd68 rip = 0x00007ffc369fa040 Found by: stack scanning 16 opencl-clang64.dll + 0x230236 rsp = 0x0000002ffeffdd80 rip = 0x00007ffc32f30237 Found by: stack scanning 17 opencl-clang64.dll + 0x3b65d87 rsp = 0x0000002ffeffdd98 rip = 0x00007ffc36865d88 Found by: stack scanning Thus in your case first of all try to disable the OpenCL hardware acceleration ... Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2 Link to comment Share on other sites More sharing options...
Alexcla01 Posted December 28, 2023 Share Posted December 28, 2023 (edited) I want to report that yes, the crashes are consistent and repeatable, I go and cut an image save and then open a new one, press the auto levels or contrast and it just closes I even did re-install windows, I was on windows 11, I try windows 10 y the same happen, I try an older nvidea driver and the lastest and nothing, disable Open CL did nothing aswell. in both cases windows 10 and 11 were updated to the lasted patch of dicember. I need it to do my work today and I barely made it possible, I can't believe how unstable affinity is, my pc is not even old specs: i7 12700, 32gb of ram, RTX 3060 12GB, and SSD MVme PCe 4.0, I use older version of photoshop and never experience a crash, heck even Paint Tool Sai is rock solid even when the program is on development, what's going on?? I find a comment after already purchased the software... "they really drop the ball with 2.0" I really wish could buy the 1.0 version, some people say is really solid. I'm actually thinking of asking for a refound, is not even a mount since I purches the software, but 14 days is what they give you... so not much I can do... just wait for more updates. Edited December 28, 2023 by Alexcla01 mistakes from my part, english is not my native language Quote Link to comment Share on other sites More sharing options...
Komatös Posted December 28, 2023 Share Posted December 28, 2023 Hi @Alexcla01 and welcome to the forums. You may have damaged or outdated .NET components. Please check this with the .NET Framework Repair Tool. https://learn.microsoft.com/en-us/dotnet/framework/install/repair Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296) AMD A10-9600P | dGPU R7 M340 (2 GB) | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) Affinity Suite V 2.4 & Beta 2.(latest) Better translations with: https://www.deepl.com/translator Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF Life is too short to have meaningless discussions! Link to comment Share on other sites More sharing options...
v_kyr Posted December 28, 2023 Share Posted December 28, 2023 9 hours ago, Alexcla01 said: I want to report that yes, the crashes are consistent and repeatable, I go and cut an image save and then open a new one, press the auto levels or contrast and it just closes Provide an Affinity crash report (if there is some) ... Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2 Link to comment Share on other sites More sharing options...
Alexcla01 Posted December 28, 2023 Share Posted December 28, 2023 I'm here to report that the .net repair tool did nothing, I did try to install .net dev and the .net offline installer and nothing. windows 10 completely updated, a clean install as well 2023-12-28 12-46-41.mkv bc843f38-c9a3-470d-887f-fb803aedfb75.dmp 46d3b274-e8b3-4af4-98f6-4558d583b257.dmp 9172c2a9-a6e5-4d4c-8de0-baac9b1d19e5.dmp af2a84d8-8a65-4825-a323-c75cb3947f61.dmp de5850c5-6425-496f-8fa3-df17bf7bdb61.dmp Quote Link to comment Share on other sites More sharing options...
HVDB Photography Posted January 7 Share Posted January 7 @Torstein There's a way to use Affinity Photo more efficiently. My .afphoto file (see attachment) is half the size of yours ! That's because I'm only using one layer to apply all the adjustments. First I made a selection (selection brush) of the parts that needed to be blurred. Then I did save that selection as a spare channel and renamed it "blur" (see the channels panel). If you right click on the spare channel and choose "Load to pixel selection" you can reuse it at any time. I also saved that selection in a file (see attachment). Via menu: "Select > Invert Pixel Selection" you can switch back an forward to manipulate the opposite part of the image. Now with the selection active add an adjustment layer and make changes. These changes will only be applied to that selection. Hope this was helpful. Vintermåker_adjusted.afphoto Vintermåker_adjusted.afselection Quote Affinity Photo 2.3.1 Laptop MSI Prestige PS42 Windows 11 Home 23H2 (Build 22631.3007) - Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz 2.00 GHz - RAM 16,0 GB Link to comment Share on other sites More sharing options...
v_kyr Posted January 7 Share Posted January 7 On 12/28/2023 at 7:52 PM, Alexcla01 said: I'm here to report that the .net repair tool did nothing, I did try to install .net dev and the .net offline installer and nothing. Though your provided crash reports do always indicate ... Quote Thread 0 (crashed) 0 Serif.Interop.Persona.dll + 0xe48b5d rax = 0x0000000000000000 rdx = 0x0000000000000200 rcx = 0x0000a00000000000 rbx = 0x0000021d395e7f80 rsi = 0x0000000000000200 rdi = 0x0000003c3c3fe770 rbp = 0x0000021d41bf0870 rsp = 0x0000003c3c3fe4d0 r8 = 0x0000003c3c3fe770 r9 = 0x00007fff1bfcd868 r10 = 0x0000000000000000 r11 = 0x0000000000000246 r12 = 0x0000003c3c3fe770 r13 = 0x0000000000000200 r14 = 0x0000000000000200 r15 = 0x00007fff1bfcd860 rip = 0x00007fff193a8b5d Found by: given as instruction pointer in context 1 mscorlib.ni.dll + 0x6b427 rbp = 0x0000021d41bf0870 rsp = 0x0000003c3c3fe4e8 rip = 0x00007fff1c15b428 Found by: stack scanning 2 clr.dll + 0x2ba110 rsp = 0x0000003c3c3fe4f0 rip = 0x00007fff1d9ba111 Found by: stack scanning ... ... that the mscorlib.ni.dll (Microsoft Common Language Runtime Class Library) and clr.dll (.Net Common Language Runtime), which are both parts of the .Net framework, to be here execution wise involved into the crash problems, when Serif's interop persona DLL finally crashes. Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2 Link to comment Share on other sites More sharing options...
Alexcla01 Posted January 7 Share Posted January 7 sadly, even if it is a .net framework issue, I try installing windows from scrach and nothing, windows 11 o windows 10, windows with no .net updates and nothing as well, I try to updated .net manually and nothing, at the end it looks like is a issue with affinity, because nothing works, nvidia drivers or Vredist and nothing, I don't think it is my hardware, the only thing that change recently was my cpu, I updated from i5 12400 to an i7 12700, games and other programs work fine, gimp or krita, heck even recently I try Photoshop CS2 and it did work.... so yeah I sail the high seas... I was desperate and I needed the software for my work, I'm considering photoshop essentials, because I don't like subscriptions, even though is limited it will do. anyway the point is I tried a lot of things and nothing work, too bad is already paid so... I'll wait for future updates on the software. Quote Link to comment Share on other sites More sharing options...
v_kyr Posted January 7 Share Posted January 7 1 hour ago, Alexcla01 said: anyway the point is I tried a lot of things and nothing work Is hardware acceleration, aka OpenCL support already disabled under the Affinity preferences? Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2 Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.