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

Search the Community

Showing results for tags 'crashed'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.2 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 13 results

  1. I have tried restarting the program, restarting my computer, turning off all other applications to reduce RAM usage, turned off antivirus/malware, saving the file with 1/3 of the pages removed, resaving the file with lower DPI... yet it doesn't stop the crashing. I have attached all the crashes so far today. If you need a copy of the file itself to test then it would need to be private because it is a yearbook for a school. Thank you for your help! I need to get this to the printers ASAP but I can't export to PDF with facing pages. I need an internal bleed and facing pages makes the bleed from the opposing page save onto the page even if I export as pages instead of spreads. The only way I have figured out how to do this is by turning off facing pages THEN exporting as pages. Jessyca 2d351e03-d872-4b2c-b488-8d24e66243da.dmp 6a876d4d-94dc-492e-b469-8b615b439728.dmp 8570f8ce-16d7-4e86-9de2-bef384fed12b.dmp 0a9e24b9-91ad-4608-97f8-9facc894b911.dmp d249d8f9-c622-4705-83dc-9333dfdc7c1f.dmp 7c2982f3-6ab7-4ea3-b88a-5d42f031c012.dmp 36f2908d-4e8e-4ca8-9b20-a217495142d5.dmp f6e7abf2-76ba-4989-ba45-342a765e96c1.dmp
  2. My affinity designer and publisher is useless on my pc... When I open the software> New File> IT JUST STOPPED RESPONDING. I have to close in task manager. WHYYYY??? 😠😞
  3. I updated to 2.1.1 today. It launched upon completion, and I created a file and then closed the program. Everything was working fine. Then an hour later, I tried opening it again, and it immediately closes and disappears after opening. I dont click, it just, closes instantly. I tried clearing user data doing the hold Ctrl trick. I reinstalled, I reverted to 2.0.0 and even 2.0.0 will not open. Immediately closes upon opening in the exact same way. This program is an important piece of my job, I need a patch asap or I will have to reinstall v1 Edit: Turns out now Publisher and Photo will also now not open. Updating to 2.1.1 completely broke the entire suite.
  4. Here's the problem I have, the software crashed whenever I try to type the typeface's name. Any other softwares are working fine on my pc just this keep crashing. 2022-10-17 11-03-40.mp4
  5. Ok now it's becoming very annoying. AD crashes at least once a day. It crashes when exporting using Export Personna, when copying layers from a document to another (I already reported those 2 bugs). And now it just crashed while I was croping an image. I'm using AD from the first version, I was very enthusiastic at the begining. But I start thinking that this app cannot be used in a professionnal way. Can someone from the Affinity team tell me that those bugs are known and will be corrected soon ? Please stop making new features for now and focus on resolving bugs. I really don't wanna go back to Illustator. Thanks affinity_crash.txt
  6. Hello, I recently purchased your software as all the videos showed how well it works for astrophotography. I was particularly impressed with how fast your stacking process was in your videos. However, each time I use your Astrophotography Stacking process, once I hit stack the whole programme just crashes. I left the programme alone for over an hour. Not even Deep Sky Stacker takes that long. This is deeply disappointing and contrasting to what your videos demonstrate. My laptop has a i7 quad core processor too so it's not exactly slow or lacking power. Please can you provide me with support on this issue? I have attached a screenshot here (using my phone as I can't grab a screenshot due to your programme crashing every time).
  7. I have a deadline tonight but Publisher keeps crashing. Always when I try to save but also occasionally (on auto save?) not sure. file previously worked and saving / modifying worked fine
  8. Affinity Photo 1.8.3 crashed twice while saving a quite big photo (1.6GB) on Windows 10 (Version 10.0.17134 Build 17134). This was very disconcerting in an otherwise quite positive experience. These are Windows event viewer logs for the occurrences: Log Name: Application Source: Application Error Date: 2020-07-04 13:54:59 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: redacted Description: Faulting application name: Photo.exe, version: 1.8.3.641, time stamp: 0x5e833198 Faulting module name: ucrtbase.dll, version: 10.0.17134.677, time stamp: 0x9f346d3f Exception code: 0xc0000409 Fault offset: 0x000000000006ca78 Faulting process id: 0x3948 Faulting application start time: 0x01d651e4291e6cd4 Faulting application path: C:\Program Files\Affinity\Photo\Photo.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: c68a352f-15c4-47d1-9f7b-afe45b5c8311 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-07-04T11:54:59.599830800Z" /> <EventRecordID>163745</EventRecordID> <Channel>Application</Channel> <Computer>redacted</Computer> <Security /> </System> <EventData> <Data>Photo.exe</Data> <Data>1.8.3.641</Data> <Data>5e833198</Data> <Data>ucrtbase.dll</Data> <Data>10.0.17134.677</Data> <Data>9f346d3f</Data> <Data>c0000409</Data> <Data>000000000006ca78</Data> <Data>3948</Data> <Data>01d651e4291e6cd4</Data> <Data>C:\Program Files\Affinity\Photo\Photo.exe</Data> <Data>C:\WINDOWS\System32\ucrtbase.dll</Data> <Data>c68a352f-15c4-47d1-9f7b-afe45b5c8311</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Log Name: Application Source: Application Error Date: 2020-07-04 21:35:55 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: <redacted> Description: Faulting application name: Photo.exe, version: 1.8.3.641, time stamp: 0x5e833198 Faulting module name: ucrtbase.dll, version: 10.0.17134.677, time stamp: 0x9f346d3f Exception code: 0xc0000409 Fault offset: 0x000000000006ca78 Faulting process id: 0xee4 Faulting application start time: 0x01d651f9fdaf2343 Faulting application path: C:\Program Files\Affinity\Photo\Photo.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: a0f7dec5-9ce5-4989-9676-2d2d9bbb5da4 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-07-04T19:35:55.822077500Z" /> <EventRecordID>163852</EventRecordID> <Channel>Application</Channel> <Computer>redacted</Computer> <Security /> </System> <EventData> <Data>Photo.exe</Data> <Data>1.8.3.641</Data> <Data>5e833198</Data> <Data>ucrtbase.dll</Data> <Data>10.0.17134.677</Data> <Data>9f346d3f</Data> <Data>c0000409</Data> <Data>000000000006ca78</Data> <Data>ee4</Data> <Data>01d651f9fdaf2343</Data> <Data>C:\Program Files\Affinity\Photo\Photo.exe</Data> <Data>C:\WINDOWS\System32\ucrtbase.dll</Data> <Data>a0f7dec5-9ce5-4989-9676-2d2d9bbb5da4</Data> <Data> </Data> <Data> </Data> </EventData> </Event>
  9. Hello Guys, Would REALLY appreciate your help if you're able to assist me on this one. So I recently was doing some general house keeping, moving some files to correct locations, etc etc and all of a sudden these few file will NOT open at all. As soon as you see the project open it crashes Publisher completely. Please note: these were opening fine in their new location so I know it's not because they have been moved and even still, it shouldn't crash an app even if it was. I have absolutely no idea why this is happening. I have reinstalled Publisher but to no avail. Crash report is attached. Any ideas? Many Thanks, Scott publisher-crash-report.txt
  10. To whom it may concern, I just bought the Affinity Designer App with my old MacBook Air and the Mac crashed a week after I bought the Affinity Designer App. I bought a brand new Mac and now when I go to download the new Affinity Designer App with the same exact Apple ID it is saying I have to purchase it again. Do I really have to buy it again?
  11. Hi, I have a user that is using your hard and software for Affinity and equinox 2.0. It was installed on PC1 for years and worked without any problem, suddenly it stops working. I tried to re-install the software from the CD-rom gotten at purchase, everything is fine until i try to open the .exe file and it instantly crashes(xxmodulesuite has stopped working, windows is looking for a solution) the computer has all the requirements thats asked for, I am running windows 7 with all the latest windows updates. I installed it on a similiar specs machine with Windows 7 and it works without a problem. Could this be a driver issue? I have not yet checked that all the drivers are up to date. Best regards
  12. Affinity Photo 1.5.0.37 (Beta) Windows 8.1 64bit. I made a selection with the Selection Brush, which went well but going to Edit/Copy the program crashed. I repeated the operation several times but got the same result. This was disappointing as on earlier versions I created several composite images flawlessly. Please advise.
×
×
  • 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.