Jump to content

Search the Community

Showing results for tags 'memory'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity 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 22 results

  1. Hi! After using Publisher 249 for one to two hours, my computer freezes or goes utterly slow. After waiting a few minutes it is possible to close Publisher and get the computer up to speed. This behavior is a clear sign of a memory leak. Using Publisher 249 on windows 10
  2. multiple artboards (40+), document around 130MB, whole document area ~10k x 10k pixels constantly falling without any notice. Opened file, placed image -> killed and exited to windows. Reopened, tryed to zoom, again. Then reopened and worked for 2hrs without problem. have 32GB RAM, fast ssd disks, win 10, latest beta.
  3. Hello, I have seen many beautiful complicated works done by affinity designer and those were done on ipad or older versions of iMac and windows pc whose configurations are unknown to me. That gives an impression that designer is not very resource hogging. My question is how complicated is too much for my windows pc (G4560, 16Gigs, igpu, 250gig ssd)? I'm not quite asking the system requirement to run designer. I'm asking after what point my computer may start lagging? Like multiple layers or bigger canvas or too many raster brush - what will be the choking point of my pc? In that case, I'm thinking of doing small upgrade. What I can invest in? Thanks in advance.
  4. Hey guys, Thought I'd share this here in case anyone else has experienced this. In Affinity Designer (v1.6.5.123 windows 10), my colour picker (when dragging from the tool above the colour palette area) starts to slow down the longer a document remains open. The dedicated colour picker tool from the left-hand toolbar remains unaffected, only the drag and drop style one experiences the lag. It's smooth and responsive when exiting and reopening Designer. Designer is currently sitting at 700mb memory usage and my machine has 16GB. None of my other resources are capping out when I perform the action (i5 6600, 16GB RAM, GTX 970). I haven't necessarily timed how long it takes for the lag to start occurring but it's probably around the hour mark. If I open a new document the lag is still there until a restart Designer. It's not the end of the world, just something that the devs might want to try reproducing!
  5. Hello Dear Dev, i have one question that can also be taken as a suggestion for the entire Affinity product line (Designer, Photo and Publisher), have you ever though about implementing a scratch/swap/cache disk/technology ? i mean, evolved softwares uses that functionality to help their product not kill the weakest port of the system which is the RAM. Well affinity products runs well but ... by making it possible for us to setup a scratch or swap space that is directly on our Hard Drives will help us doing better and working with less stress. To give an exemple just check how linux works with swap space. There are lots of people who uses Affinity line because they can't afford the rock start products which requires to upgrade the hardware again and again. Making it possible for users to setup that space directly on their physical drives will change lives as one will personally estimate how big the scratch/swap/cache space will be and work no stress (for those who may go up to 30 or 40GB swap/scratch space. That space must be cleanable in many ways: 1- From the software itself (in its launched state) a line in the File menu saying : Clear scratch/swap/cache content. 2- From the Preference center just add it to Miscellaneous section : reset or clear cache/scratch/swap content. 3- Must be clearable when doing the full software reset combo. 4- Must be cleanable with usual cleaning tools. Trust me guys, implementing this will make things even better and i believe there are geeks here who can help making this even clear for us. Blessings !
  6. ToM912

    Memory Issues WIN10

    Dear Serif / Affinity Team, thanks for the incredible Affinity Designer Tool. I enjoy to work with it very much. After a few months of inactivity, I continoued working on a few mockups for an application. My setup: OS: Win 10 64-Bit Affinity Designer 1.6.4.104 PC Hardware: HP Z Book 15 G3: i7-6820HQ 2,7 GHZ, 16 GB RAM Unfortunetly the allocated memory of Affinity Designer increases rapidly and keeps the OS busy until Affinity Designer crashes or my PC crashes (including Bluescreen). When I started Affinity Designer with my Assets (assets file ~38 MB), it already allocates round about 5GB of RAM. When I load my mockups additionally, the total allocated RAM goes up to the full 16 GB. (12 GB by Affinity Designer). The project file is about 26 MB or 41 MB big. After that I removed my assets to see if Affinity behaves differently. Unfornetly, when opening my project file, the allocated RAM rises again up to 16 GB (~14 GB by Affinity Designer). Are there any restrictions regarding the filesize? How can I improve the behaviour to work again? Hope to hear from you! Thanks in advance. Best regards, Tom
  7. eyeclick

    Memory Leak on Photo

    I'm having memory leak issue with Affinity Photo. On my desktop (Window 10) I had to shut it down when it took over 5 gigs of memory. I copied all the files I was working on to my laptop (also Win 10). I have two full layers that are from a 24MB file and two more with small sections I'm cloning. The file size is huge at 499MB and the ram usage is 10.5 Gigs! I closed all files and left the program open. After a few minutes it went from 10Gigs to 8,5Gigs. With no files open. 10 gigs should be enough for 400 24MB files. If it saved every stroke as a new file it should still have room. Photoshop would add the original file size for each layer, but this seems to be an order of magnitude larger.
  8. Affinity Photo is nearly unusable for me due to a major bug that is somehow related to a task in Task Manager called Usermode Font Driver Host. My system is quite adequately fast for all other tasks, but as soon as I open Affinity Photo, the task mentioned bloats up to 30% to 40% of CPU capacity. It might as well be 100% or 300% because the entire computer is frozen to death. Can't use any other program, and Affinity does not respond in the slightest. It takes several minutes just to open the Task Manager in order to kill Affinity. If I wait quite a long time, the font task seems to settle down a bit. It's clearly related to Affinity though because as soon as I am able to kill Affinity, the font task immediately goes back down to zero CPU (or just goes away), and my computer becomes usable again. In addition, I didn't have this problem at all on my computer until Affinity was installed, so it must be related. I also saw another topic on this forum related to this task, and the author of that post also mentioned Affinity Photo. There were tons of responses, but the topic was eventually closed, so I couldn't post a "me too" reply there. If this continues and there isn't a patch or settings fix for it, I'll have to ask for a refund because the software is completely unusable. It's sad because otherwise I see the software as being quite formidable and fun to use (though it could use a bunch more features and minor fixes - which I can see the development team is fairly quick to implement or at least add to a coming soon list) For the record, I'm a long time user of Serif software. I own nearly all the previous "Plus" titles, and some years ago I was very active on the forums, Flickr group, and I even beta tested a number of titles. I was excited to see Affinity get so much press... I'll be disappointed if I have to let it go in favor of other more stable apps.
  9. Hi, Affinity photo is VERY slow on my old iMac (21.5, mid-2010, 3,6 GHz Intel Core i5, 12 Go).It takes ages to open, export, etc. I checked with activity monitor and it uses an incredible amount of memory (see attached file). I can hardly use it.
  10. Hello, I use MacBookAir i7 8g 512SSD (11pol) How best adjust for economy battery???? . OpenGL ativate??? . Use only GPU Integrated??? Help
  11. SailorMax

    Memory/CPU optimizations

    Tried to open few ARW files at once, but Affinity Photo tried to open them too slow (I waited few minutes and has to kill it). For test tried to open only one photo and compare result with Photoshop: Affinity Photo 1.6.0.89: - init used memory after cold start = 184MB - time to show = 14 seconds - time to finish open = 52 seconds - used memory = 1,268MB Photoshop CC 2015: - init used memory after cold start = 143MB - time to show = 4 seconds - time to finish open = 14 seconds - used memory = 489MB Sample attached to this post. Try to make 10x duplicates with different names and drag them all to Affinity Photo... In result on my system currently I can work with Photoshop, but not with Affinity Please, optimize your product. System: - CPU: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz - GPU: Geforce GT 240 - Memory: 4GB - Free space on disk: 50GB - OS: Windows 10 1709 b16299.19 _DSC6435.ZIP
  12. Hi, After upgrading Designer to 1.5.3 its starts to eating my memory even on quite small files (about 5 fullhd art boards). After 20 minutes of work, every move I make takes between 2 and 5 seconds for Designer to response. I found that weird because it even does not touch my hardware limits. Eats about 1.5 GB of RAM and uses between 15% and 20% CPU. I have 16 GB and Intel Core i7-3370. Already tried decreasing undo limits to 32, and that helped a little but still its very annoying and I have to restart Designer every 15 minutes. Is there anything I can do? Cheers, Radek
  13. I have posted previously with no joy but Photo v69 is crashing on even the most innocuous of tasks. I cannot do an HDR Merge with Tone map checked as it will shutdown my PC. I am having to work around the program to get it to do the fundamentals. I currently have an 4.5mb image open and Task Manager is showing it as consuming 600mb of ram with no processes being undertaken. At one point I had Task Manager open when I ran an HDR merge and it indicated that photo.exe was consuming 2.9gb of memory. I have just tested my image and applied the Tone Map persona and watched Task Manager creep up to 2.8gb before my PC crashed and rebooted itself.....This cannot be right and needs to be resolved.
  14. After working intensely in a 300+ mg AD doc, certain AD functions no longer work. Quitting AD and bringing it up again solves the problem, and AD always remembers what I had just done (bravo!). I'm working with a MacPro with 24g of RAM with nothing else up except Mail. Does AD only access a limited amount of memory? Is the problem that its Undo remembers everything I've done in the session since I am manipulating many layers with hundreds of object? It may simply be a Mac memory problem. No big problem. Just wondering what the cause might be.
  15. open up 25 canon RAW files, 80D, 24MP. AP grinds to a halt. doing anything to develop the image is nothing but extreme sluggishness and beachballs. open task monitor and the answer is clear, AP is allocation very large chunks of RAM per image. I have a brand new MBP 15" 2016 TB and I'm stuck at 16gb whether I like it or not. So its very easy to hit this limit. In task manager, AP is taking about 9gb of real ram and another 8gb of compressed ram that spills into VM. Once VM is involved things grind to a halt as RAM is compressed / expanded and swapped to disk, even on the super fast 2GB/sec SSD on my machine. Even adjusting prefs to tell AP NOT to use all the RAM in the machine ( default setting, another bug ) it still over flows and used more RAM than allocated to it. AP should never try to use 100% of the RAM for obvious reasons. At best it should maybe be 50-65% as a default value, but then actually respect that setting. On OS X I find the OS + maybe a few small apps like email use about 4.5 to 5gb of RAM at idle. That aside, it seems that SP is allocating just under 1gb per image where the image = 6000X4000 @ 16bits. it should be about 192mb for that image @ 16 bits in RGBA. even another full size buffer is 192X2. looks like AP is allocating 4 additional image buffers to burn thru RAM like that. way too much. perhaps a user pref is needed to tell AP how many image buffers to use per image.... In comparison, PS can have this many images open w/o slow downs, beachballs, etc so AP needs to fix how it is allocating RAM to respect the users settings in prefs on how much to use, and to avoid spilling into comressed RAM and then VM for a HUGE performance hit that brings the app to a near standstill. The workaround : only open a couple images at a time to avoid running out of RAM :(
  16. Hello! I encountered this during a stitch of a relatively large panorama yesterday. I'd assume it's just a glitch somewhere in a statistics calc, but my inner mathematician is twitching from seeing an efficiency over 100%. You can view it in the bottom right corner of the attached image. I also couldn't find much info in the help files about these stats (Memory Pressure/Efficiency) in the help file, and most of the google search results seem specific to OSX. Is there a good explanation available somewhere for them? Thanks! Pete
  17. RosomakPL

    Ram Usage

    Hello, I Just installed Affinity Photo Trial, and have I scored first crash. In preferences/performance is "ram usage limit" why it is possible to set a higher value than available phisical memory? Accidentally I touched the slider... Affinity uses by default all available ram. I have 16 GB and in preferences/performance is assigned all. Seriously? How about to leave some for other apps? Or system processes?
  18. Hello, We attempted to open 14 Nikon RAW files (NEF) from the Affinity Photo menu "file/open", and selected the 17 files. The memory usage of the application shot up to 13.7 Gigabytes of RAM I have attached a screenshot (dual monitors) for your review. We are running Windows 7 Ultimate 64 with SP1 on an i7 CPU with 16GB of RAM. Please advise... Mark
  19. All, I am building a new Windows 10 pc for photo editing and shoot mostly in raw and am trying to work out the following for affinity photo. 1. Is there any advantage in using INTEL cpu over AMD? 2. Is there any benefit going from SSD do m.2 SSD and the speed that can be obtained through them? 3. Do any particular graphics cards offer benefits over other types IE Quadro vs GTX? 4. I am looking at getting a 27 inch monitor (maybe 32) is there any real world benefit for going to (IPS) 4k over WQHD? Any thoughts please? Thank you Al
  20. I did an SVG conversion on a jpeg and when I open it in Affinity my machine falls over (memory issue). Machine has 8GB Physical ram and 4GB Video ram. Weirdly, I can open the file and work with it very comfortably in Inkscape Is there anything I can tweak to avoid this issue in future? Are SVG's problematic in Affinity? Is there another format that it might play nicer with? Thanks J memory hog.svg
  21. Seit heute kann ich keine Raw-Dateien (Fuji-RAF-File) mehr laden. Photo zieht sich unendlich viel Speicher und bricht dann ab.
  22. This is absurdity! I will describe it briefly, because my English is bad. I wanted to merge objects (it was 31 objects) - it still takes longer than 10 minutes! I still waiting for effect ... I look to monitor activity, and there .. Check it screenshot. More than 26GB of memory usage?!?! My iMac Mini has 16GB. It's probably a bug or..? - how about that? When I finish this post it's now 20 minutes and still nothing. I guess I'll have to reset the AD. Any ideas? Btw, other programs and functions work flawlessly at that time. Cheers!
×