Jump to content
You must now use your email address to sign in [click for more info] ×

Several crashes after 2.2.0.2005 update


Recommended Posts

Did you get any crash reports?

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

  • Staff

We have seen a number of crashes over the years with Capture One. Though, saying that, I cannot recall a recent 'known' issue with it. If you do a quick search you will find a few crashes related to it, along with some workarounds.

I'd be interested to see the crash report if you have one.

Link to comment
Share on other sites

I have been getting crashes and slow responses in Photo 2.2.0.2005. Crashes seem to occur when making flood selections. Saving files seems to take 2 passes with the first pass taking several seconds to complete. I have a Windows crash dump file if that's of use.

Link to comment
Share on other sites

21 hours ago, PhilH said:

I have a Windows crash dump file if that's of use.

17 hours ago, PhilH said:

C:\Users\philh\.affinity\Photo\2.0 (Beta)\CrashReports\reports

Folder is empty

If there isn't any Photo 2.2.0.2005 related crash report file, but instead Win dump ones, then APh probably crashes early before having a chance to initiate the out-writing of an own crash report file.

17 hours ago, Steve Wimbledon said:

Doh! Right next to AppData. sorry

So does this crash report stems from a time when C1 was also running? - Though the crash report seems to be more for Photo.exe  2.2.0.1994 here than 2.2.0.2005.

For that 2.2.0.1994 here then it looks like the .Net CLR interoperation with kernelbase.dll get's puzzled in order to access APh in memory wise the right way, as an ACCESS_VIOLATION_READ exception is generated ...

Quote

Operating system: Windows NT
                  10.0.22621 2215
CPU: amd64
     family 6 model 158 stepping 13
     6 CPUs

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x0000000000000000
Crashing instruction: `nop dword [rax + rax * 1]`
Memory accessed by instruction:
  0. Address: 0x0000fff8121dad08
     Size: 4

Process uptime: 118 seconds

Thread 0  (crashed)
 0  KERNELBASE.dll + 0x6531c

     rax = 0x00007ffc090ed684    rdx = 0x000001b7c903e2e0
     rcx = 0x0000000000000000    rbx = 0x0000000000000000
     rsi = 0x000001b7cb0ee488    rdi = 0x0000000000000000
     rbp = 0x0000000000000000    rsp = 0x0000007f293fd910
      r8 = 0x0000000000000000     r9 = 0x000001b79b867620
     r10 = 0x0000000000000000    r11 = 0x000001b7c8f20140
     r12 = 0x000000000000c350    r13 = 0x000001b7cce81f98
     r14 = 0x0000000000000000    r15 = 0x0000000000000000
     rip = 0x00007ffc4643531c
    Found by: given as instruction pointer in context
 1  clr.dll + 0x181242
     rsp = 0x0000007f293fd9c0    rip = 0x00007ffc09221243
    Found by: stack scanning
 2  clr.dll + 0x18e718
     rsp = 0x0000007f293fd9f0    rip = 0x00007ffc0922e719
    Found by: stack scanning
 3  clr.dll + 0x18e74a
     rsp = 0x0000007f293fda20    rip = 0x00007ffc0922e74b
    Found by: stack scanning
 4  clr.dll + 0x7e72b7
     rsp = 0x0000007f293fda58    rip = 0x00007ffc098872b8
    Found by: stack scanning

 

☛ 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

Ok, yes C1 was running at the time all four crashes occurred. I know there were three beta updates in quick succession, I may not have installed 2005 by then but I thought I had! So it looks like it was simply APh just caused a read violation? I’ll try and recreate without C1 running. Thanks for looking into it. Hope you guys continue to flourish and get us to buy major updates at reasonable cost. Once you’ve got all of Adobe’s customers you’ll need to generate a bit of income. Keep it up 👍 

Link to comment
Share on other sites

30 minutes ago, Steve Wimbledon said:

So it looks like it was simply APh just caused a read violation?

That shouldn't happen and it has to be find out how to prevent this for future by the Affinity dev team.

31 minutes ago, Steve Wimbledon said:

I’ll try and recreate without C1 running.

Try out both with and without C1 running but use the official released v2.2 build now instead!

☛ 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

I have tried over and over to crash both the new 2.2 general release and beta 2005, doing everything I was doing last week but can't recreate. (whether Capture One running or not)  I guess sometimes computers just fall over. Will definitely provide a 'dump' if it happens again. Thanks for taking the time.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.