Jump to content

Search the Community

Showing results for tags 'high cpu in not responding state'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hi, TL:DR Set Fill / Paint / font colour change crashes the program when applied to a block image e.g. not a font. Attempts to paint the entire A4 page but takes 15 minutes perhaps more. Why does it take so long to paint a page. Why did it paint a page when it was only a small portion that was selected. Improve logic to prevent this? Hardware i5 2500K overclocked to 4.1gHz, 8GB RAM, 128GB ssd, Intel onboard Graphic 3000, 4TB ssd/plater HD, AMD 5770 1GB video card Creating another master piece and was just changing the colours of the fonts. I then clicked on a block of graphic image and clicked on that to change its colour. Once I did this the computer started to play up with the mouse becoming erratic e.g. not moving smoothly. This got worse to the point I had no response from my computer. After a minute approx I could get taskmanager to start and I could see that Affinity Photo was reporting it is "not responding" At first it was using 1% cpu and 1.5 GB of memory Being patient I waited perhaps another 5 minutes perhaps 10 and noticed that the program came back sort of. I checked taskmanager again and found that cpu use had risen to ~32% and 4.5GB of memory with 0.3% of disk activity. The entire Affinity Photo program screen had a transparent grey all over the entire screen. Normally when I see a program in this state I would conclude it had crashed. I waited some more and found the program returned to a functioning state however my entire image had be painted the font colour. At first I didn't realise it had done this but as I clicked on the image I noticed handles responded. I saved the file "which had ballooned from 2MB to 27MB" in this state and restarted the program and found the entire image was still completely painted in the font colour. I used the undo feature and managed to get the image back to where I wanted it. I then attempted to change the colour again of the block image and guess what it did exactly the same thing and "crashed" I took screen shots including the taskmanager if your interested. The saved files seemed excessively large as for an A4 size page. It is a very basic image with text a certificate of a swimming milestone for ABI swimmers. Thought I would have had this done and dusted in say an hour or so but I have spent a considerable amount of time on it due to the "crashes" and writing in this forum. Images blurred for privacy reasons.
×