Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

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
    • Report a Bug in Affinity Designer V2
    • Report a Bug in Affinity Photo V2
    • Report a Bug in Affinity Publisher V2
    • Report a Bug in Affinity Version 1 applications
  • Beta Software Forums
    • macOS Beta Forums
    • Windows Beta Forums
    • iPad Beta Forums
    • [ARCHIVE] Reports from Affinity Version 1 Betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


Skype


Facebook


Twitter


Location


Interests


Member Title

Found 7 results

  1. 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
  2. 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
  3. 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
  4. 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).
  5. 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>
  6. 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?
  7. 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
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.