https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
Kelson [Emmanuel Engelhart] changed:
What|Removed |Added
CC||kel...@kiwix.org
--- Com
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
Bawolff (Brian Wolff) changed:
What|Removed |Added
CC||aklap...@wikimedia.org
--- Com
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
Bawolff (Brian Wolff) changed:
What|Removed |Added
Blocks||16456
--
You are receiving th
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
Bawolff (Brian Wolff) changed:
What|Removed |Added
CC||wulong.su...@gmail.com
--- Com
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
Bawolff (Brian Wolff) changed:
What|Removed |Added
Summary|No thumbnails for some |out of memory for some
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
PRO changed:
What|Removed |Added
CC||perheli...@gmail.com
--- Comment #2 from PRO --
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
--- Comment #10 from Bawolff (Brian Wolff) ---
Hmm, I was recently testing image magick, and it seems to have better memory
performance then older versions, with me being able to scale a bunch of images
locally that don't work on cluster.
--
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
--- Comment #11 from Bawolff (Brian Wolff) ---
Created attachment 15694
--> https://bugzilla.wikimedia.org/attachment.cgi?id=15694&action=edit
mem limit values I tested image magick with
So in my tests, newer versions of image magick seem to
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
--- Comment #4 from Bawolff (Brian Wolff) ---
(In reply to PRO from comment #3)
> Sorry my correction, the limitation is not somehow 12.5MP it is above ~23 MP
> (and seems for sure as of 26 MP, dependence by the frame size I've not
> tested). I
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
Dominic changed:
What|Removed |Added
CC||mcdev...@gmail.com
--- Comment #5 from Domin
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
--- Comment #6 from Bawolff (Brian Wolff) ---
(In reply to Dominic from comment #5)
> This may be a separate issue, but that error message is particularly
> unhelpful. When you hit the MP limit, at least you get a message for that,
> in theory.
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
--- Comment #7 from Dominic ---
It may not help the average user experience (though if they are hitting this
error, I am nit sure they can be helped), but I was just thinking how
frustrated I get at vague error messages, which I can't look up t
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
--- Comment #8 from Marco ---
(In reply to Dominic from comment #7)
> Would actually writing out "out of memory" actually be anymore helpful? I
> cant imagine that that means much to average user.
Maybe not the average user but the uploader may
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
--- Comment #9 from Bawolff (Brian Wolff) ---
Different error: oom can be triggered by different but related conditions. Tiff
files can also be oom
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC li
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
PRO changed:
What|Removed |Added
See Also||https://bugzilla.wikimedia.
|
https://bugzilla.wikimedia.org/show_bug.cgi?id=61711
--- Comment #3 from PRO ---
Sorry my correction, the limitation is not somehow 12.5MP it is above ~23 MP
(and seems for sure as of 26 MP, dependence by the frame size I've not tested).
I've tested some in [[Category:Animated GIF files affected
16 matches
Mail list logo
