Could be. I know almost nothing about our rendering code and libraries. Don't know how important it is to fix it.
It is in the Release Notes now, but I don't know how many people actually read that. At least it is something to point to if someone reports a huge memleak issue. Probably not so many people use 16-bit color depth, but for my colleague on Linux does :) (only thing that works for him is Linux on 24 bits and "rdesktop -a 32")
cheers, Johan
On 5-4-2013 0:23, Josh Andler wrote:
Johan,
Is it possible that the issue is with the win32 devlibs?
Cheers, Josh
On Thu, Apr 4, 2013 at 2:27 PM, Johan Engelen <jbc.engelen@...2592...> wrote:
Hi all, A colleague today found Inkscape later than 0.48.2 unusable because of a huge memleak. He was using it in 16-bit (remote desktop). We found that on Windows 7, Inkscape 0.48.4 and trunk are unusable because of very rapidly increasing memory usage it quits because of no more available memory. Steps to reproduce:
- set Windows color-depth to 16-bit
- start Inkscape
- zoom in and out repeatedly (mousewheel)
- watch the used memory increase very rapidly in the task manager
Might be easy to fix this, perhaps some of the blitting/display code assumes a 32-bit buffer?
I've added it to the know issues for 0.48.4 and 0.49. (I remember that earlier versions of Inkscape would not even start when using 16-bit colordepth.)
Thanks for looking into it! Cheers, Johan
Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel