Ian Brockbank Posted August 19, 2016 Share Posted August 19, 2016 Hi, I have now managed to make Affinity crash twice in quick succession with a simple line. Crash report should have been sent (is there any way of viewing recent crash report references after the restart so I can report them here?) How should I be reporting bugs? Previously for the XxxPlus family betas I've used JIRA, but there doesn't seem to be any Affinity project there. Until I find a better way, I'll add the details here. Steps to reproduce: * I created a new file, A4 landscape with inches. * I drew an almost vertical line. * I set the stroke to ~4pt * I switched to the move tool and shrank the width to 0 The top 40% of the line disappeared. * I struggled to select the line, and ultimately it completely disappeared (although it still appears in the layers) * I double-clicked it the line and got the crash * This happens reliably with the file created from this (attached) I have tried to recreate the file, but the second time everything worked as I expected, so at least I have the generated file demonstrating the issue. Cheers, Ian line_crash.afdesign Link to comment Share on other sites More sharing options...
Mark Ingram Posted August 19, 2016 Share Posted August 19, 2016 Hi, the next time you start the app, you should see a dialog which gives you a crash reference. Failing that, you can find the crash reports in: %APPDATA%\Affinity\Designer\1.0 (Beta)\Crash Reports And then you can upload them to the forum. Link to comment Share on other sites More sharing options...
Greyfox Posted August 20, 2016 Share Posted August 20, 2016 Steps to reproduce: * I created a new file, A4 landscape with inches. * I drew an almost vertical line. * I set the stroke to ~4pt * I switched to the move tool and shrank the width to 0 The top 40% of the line disappeared. * I struggled to select the line, and ultimately it completely disappeared (although it still appears in the layers) * I double-clicked it the line and got the crash * This happens reliably with the file created from this (attached) I have tried to recreate the file, but the second time everything worked as I expected, so at least I have the generated file demonstrating the issue. Cheers, Ian Whilst I haven't been able to generate a crash by following your recipe from scratch, if I open your file, which appears as a blank page but with a curve shown in the layers tab, and simply click on the stroke tab, the program crashes with an Unhandled Exception Code 0xE0434352. Ian Brockbank 1 Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe Link to comment Share on other sites More sharing options...
Mark Ingram Posted August 20, 2016 Share Posted August 20, 2016 Can you upload a crash report? Link to comment Share on other sites More sharing options...
Greyfox Posted August 21, 2016 Share Posted August 21, 2016 Can you upload a crash report? Mark, A couple of times (yesterday) when I was trying this, it did say on the following restart that it had sent a report, but it mostly starts up after the unhandled exception normally. and there is nothing in the %APPDATA%\Affinity\Designer\1.0 (Beta)\Crash Reports folder. Opening Ian Brockbank's file and clicking on the stroke tab 100% of the time produces the crash here. Some times just opening the file produces the unhandled exception. I've just tried a Ctrl Key runup, all items selected, clear File->Open (file opened OK to what appears to be a blank landscape canvas, but with a Curve shown in the layers tab), see screen shot below. Click on Stroke "An Unhandled Exception has occurred. Code 0xE0434352" "Designer has stopped working....." Close program Nothing found in %appdata%\Affinity\Designer\1.0 (Beta)\CrashReports Start Affinity Designer, no error report dialogue. Patrick Connor 1 Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe Link to comment Share on other sites More sharing options...
Ian Brockbank Posted September 3, 2016 Author Share Posted September 3, 2016 Apologies. I didn't realise settings defaulted to not notifying by email, so I just thought no-one was interested :-( Crash dump attached. 6089acd5-25cd-477b-a20b-f61bb35476a1.dmp Link to comment Share on other sites More sharing options...
Staff Chris B Posted September 5, 2016 Staff Share Posted September 5, 2016 I'll log the crash so we have a record of it. The file crashed a few times in a row until I did the Ctrl runup and then it only crashed in the Stroke tab (thanks Greyfox). Double clicking the Layer crashed for me too. Doing the same on the Mac doesn't crash for me however the document just vanishes completely. Thanks guys How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Recommended Posts