Are there some size limits in SVG files?
Posted: Thu Nov 16, 2023 2:22 pm
I noticed something that looks like some sort of limit in Hollywood, unless I am just running out of memory.
I use https://www.photopea.com/ to save SVG-file, and I noticed that when I try to save it as big enough file, it will result in Hollywood (when trying to open it) saying "Cannot read file filename.svg !"
It seems that saving as 28800x16200 was still readable, but saving as 38400x21600 gave this error.
So is there some limit on SVG files in Hollywood, or am I possibly runnin out of memory or something?
There seems to some other odd behavior when saving SVG image in large pixel size when using photopea, for this before mentioned 28800x16200 file opens fine as long as I dont use "Save as" for the hollywood source file. If I save as it using different name, then even I dont change a single line of code, it starts throwing me this before mentioned error of not being able to open it.
And yes, I am saving the source file to exact same folder as the original one, so it shouldn't be a path problem, but something weird seems to happen when using "Save as" with a different name to save the source file in different name.
I use https://www.photopea.com/ to save SVG-file, and I noticed that when I try to save it as big enough file, it will result in Hollywood (when trying to open it) saying "Cannot read file filename.svg !"
It seems that saving as 28800x16200 was still readable, but saving as 38400x21600 gave this error.
So is there some limit on SVG files in Hollywood, or am I possibly runnin out of memory or something?
There seems to some other odd behavior when saving SVG image in large pixel size when using photopea, for this before mentioned 28800x16200 file opens fine as long as I dont use "Save as" for the hollywood source file. If I save as it using different name, then even I dont change a single line of code, it starts throwing me this before mentioned error of not being able to open it.
And yes, I am saving the source file to exact same folder as the original one, so it shouldn't be a path problem, but something weird seems to happen when using "Save as" with a different name to save the source file in different name.