Several crashes after 2.2.0.2005 update

[Steve Wimbledon]

Hi, Photo beta as above crashed three times while doing pretty basic cutting and pasting. However when I found Capture One was still running I closed it down and so far, not crashing again. Maybe just try some things while running C1 as that program messes up Canon camera software if it's running too.

[walt.farrell]

Did you get any crash reports?

[Chris B]

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.

[PhilH]

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.

[Steve Wimbledon]

Hi Chris, Phil, I was also making full frame selections at the time. Have you guys moved the crash reports for the beta program as there's nothing in  Roaming\Affinity\Photo\1.0\CrashReports ? 

[Jon P]

Crash reports for the betas (and retail if you remove (Beta) from the folder path) are:

%userprofile%\.affinity\Photo\2.0 (Beta)\CrashReports

[Steve Wimbledon]

Doh! Right next to AppData. sorry

0173e0b4-8e16-4a5d-8aa6-848f879c37c4.dmp 

[PhilH]

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

Folder is empty

[v_kyr]

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

 

[Steve Wimbledon]

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 👍 

[v_kyr]

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!

[Steve Wimbledon]

Ok.  I’ll reinstall the official release and try to crash it. 

[Steve Wimbledon]

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.