Jump to content

Search the Community

Showing results for tags 'unhandled exception'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests, Suggestions & Discussions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 14 results

  1. Setup: Operating System: Windows 10 Home 64-bit (10.0, Build 17763) Processor: Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz (4 CPUs), ~3.5GHz Memory: 16384MB RAM --------------- Display Devices --------------- Card name: NVIDIA GeForce GTX 1060 3GB Looking into Event Viewer, Affinity closes roughly after the splash screen and some .NET framework stuff happens. In the details I see that GTII-OSD64.dll is involved in it crashing. If I knew what the purpose behind this .dll file is, it'd help me resolve this faster, or atleast clarify that I should look elsewhere. This may be a system issue as my Photoshop app also crashes roughly after startup as well.
  2. Hi, In both Affinity Designer as well as, I cannot currently open any file, or even start a new document, without the application crashing. This is obviously really annoying as I have started a small project using the software, which worked fine, but now I have no possibility of accessing the saved file(s). I don't really understand what has changed. I have tried uninstalling and re-installing the application, to no avail. The problem first occurred after leaving the software open through a hibernation of Windows. This is on Windows 10 Pro build 17134. Detailed hardware info attached in second attachment. The error message is: "An Unhandled Exception has occurred and the application cannot continue. The Crash Reporter will be displayed after the application exits. Reference: 833df4fb-9734-43a9-8c26-a0cd1f3da7ea" (screenshot attached). As shown in the screenshot, the application shows the file as loaded to 100 %, but no part of the file is displayed yet. The same happens when clicking on New Document on the startup panel, and then pressing ok on the default settings in the New Document settings dialogue (after a very short flicker, the same message as shown in the screenshot appears, with a different reference obviously). For what it's worth, Affinity Photo appears to still work fine. Any help is appreciated. Thanks, J
  3. Background I created a 48 page document with a mix of text style, large raster graphics (1-5 MB photos), and vector graphics and two master styles, one for the cover exterior and another for the interior pages. ANSI Letter 5.5 x 8.5 pages in 11 x 8 spreads. I use a second, raster version of each full-spread photo that is blurred and saved to JPEG format. I overlay it to improve contrast. I used the default "prefers embedded files" setting. Attempts to Fix Issue Recreated document from scratch but selected prefer to link to file (much like how I use InDesign), rather than embedded. File size wasn't that different, which surprised me (43 MB for linked vs 47 MB for embedded) Crash still occurs when saving and attempting to reopen the file, throwing this reference: cb9c24ca-1885-41dc-9901-a1bc033de38a Crash occurs before any pages or graphics can load. Further Testing It appears that this is a known issue with raster graphics on Master Spread pages. I recreated the document without graphics on master spreads and it saved and loaded just fine.
  4. Hello, It's been the second time that the following error description was shown after I tried to open my file. The first time I simply began the project again, but since the second file produced the same error, I think it's a bug. To give you some context: I was working on a newspaper we had to do for a school French project. I'm working on Windows 10 (64). The error was shown, wenn I restarted the Computer after some hours and tried to continue working on the project. I saved the file on an external hard disk. I wasn't able to find a logfile so I just copied the error warning. EDIT: I uploaded the second file that isn't working and a PDF I created of my first file. Do you have any idea what could be wrong? Or is this a bug that has nothing to do with my computer or project but with the application? Thank you for your support. Greetings, Touuubie Zeitung.afpub Zeitung.pdf
  5. Hi! I haven't been using Affinity Photo for like a week and when I tried to launch it today I was not able to do it. I searched the web for any solutions but I did not find anything that would solve my issue. The problem is that when I try to launch the app, it gives me an error windows saying that an Unhandled Exception had occured and the application couldn't continue. Could you please help me solve this? I need to be able to work in Affinity asap. Thanks.
  6. I'm trying to assign a keyboard shortcut to the "Place image tool" in Affinity Designer I have tried assigning both single keys and single key with modifier keys, every time I hit the shortcut key, the software crashes and shows the attached error message(Unhandled Exception.png). Please solve this issue. Thank you.
  7. Hey! Not the first and probably will just make another topic about "unhandled exception" that happens when opening a document in AP. Copying d3d9.dll file did not help and that was the only reasonable answer I have found here, otherwise all I could find is just "thank you, noted" answers Win10/64/8/i5 Well... sh*t.
  8. Hello, I downloaded and installed the Affinity Designer Trial to test the program before I would buy it, however whenever I start it it instantly crashes with "Unhandled Exception, Code 0xC0000005" Image of said error: http://i.imgur.com/Y8j68y0.png Specs: Windows 10 Version 1703 (OS Build 15063.138) GPU: 980ti with latest drivers CPU: i5-4670k 8GB RAM
  9. Hi, i have just downloaded the Affinity Designer Trial for windows. The installation worked correctly but when i launch the program i am given the provided error. I am running fully updated windows 10 Pro 64-bit. I also get the same error when i try to launch the Affinity Photo windows trail. Any help and suggestions would be appreciated. [EDIT: SOLVED]: I followed a users suggestion in this thread https://forum.affinity.serif.com/index.php?/topic/39073-affinity-designer-trial-unhandled-exception-crashing-on-startup/ regarding using RivaTuner Statistics Server. I opened it and turned application detection level from low to None and affinity designer launched right away. I hope this helps someone with the same problem as me
  10. I am using a Microsoft surface pro 4 with Affinity Photo and every time I attempt to use the pen tool the program crashes and gives me the message: Unhandled Exception and the error code is 0x80004002. Is there way to resolve this problem so that I can use all the tools the program offers?
  11. Version, and the Unhandled Exception hitting UNDO after aplying the Transparency Tool to a Rastered layer, still not fixed. I've come testing every beta and full release of both programs, posted this bug many times, still ignoring me. Some would say "Then why you apply Transparency Tool to a rastered layer if you know it's not allowed?" Well, you need to looks at this from an usage and habit point of view. You will be sometimes working with rastered layers and sometimes with normal/editable/vector layers, so if you are working on an art for a client, and you are under pressure, and you apply transparency tool on a rastered layer, believing it's a vector one, bam then you notice it's rastered, and you hit UNDO to "undo" the steps and bam, Unhandled Exception. I'm programmer/developer, I program in Actionscript 3.0, Javascript/HTML5, Python, C# , PHP and Ruby, I know the hard work behind, but come one, an Unhandled Exception? A good programmer should always handle all the exceptions, errors and events. And it's getting annoying because the program just crashes. I don't lose my hopes that this will be fixed finally.
  12. Hello all. Affinity Photo was working fine (except for the occasional crash when Windows was left in sleep mode with APhoto open) until I tried to open a certain large RGB TIFF file. I have now tested other files and they seem to be OK. The two files I cannot open were uprezzed in Photozoom Pro 5 to a size above 200MB. Up until then, I had only uprezzed to about 197MB, and everything worked fine. Those two files are thus above your upload limit size on this forum, so I can't include them. If someone at Serif tech support wants to see them, please contact me. I have since found a workaround - namely uprezzing in Photozoom to 197MB, opening in APhoto and uprezzing the rest of the way. But I thought the developers might be interested in this exception.
  13. This bug is annoying and I'm getting very angry. I use Transparency Tool with Vector Layers, but sometimes, I'm working with Rastered Layers, and it's inevitable to forget that you are now in a Rastered Layer and not in a Vector Layer, so then you hit CNTRL + Z to undo the Transparency Tool and BAM!, "Unhandled Exception" and the program crashes. Still present since the first Beta. Reported it tons of times. I hoped it would be fixed for the final official release, and I purchased both programs, and for my disappointment, it is still present. Original topic: https://forum.affinity.serif.com/index.php?/topic/28731-transparency-tool-on-rastered-layers-unhandled-exception-bug-still-present-in-final-release/?hl=%2Btransparency+%2Btool
  14. I'm little bit disappointed and sad, that I purchased the final release of Affinity Designer, but it still have a bug that I reported many times. When we apply the Transparency Tool on rastered layers, and then hit Undo, it used to display an Unhandled Exception error message. Now it simply crashes the program. I think that if you don't want to support a feature, at least you have to show the user some message. Not just displaying an unhandled exception message that the user doesn't know what it mean. As I'm a savvy user, I read through the forum, and I then learned that it's a feature not to be implemented, to apply transparency tool to rastered layers because, and I quote [there are already many ways to achieve this]. So the obvious step would be to just display a simple message "Transparency Tool can't be applied to rastered layers". That's it. But when you apply it, nothing happens. Then you hit Undo and "oops" the program crashes. And this is something unavoidable because one does get used to apply the transparency tool in a regular basis, so when you are at a rastered layer, you unconsciously apply it, then you remember "oh, I'm on a rastered layer, snaps%&*#@!". Then you hit UNDO and "kaBoOm" the program throws a baby tamtrum. Well...