Last modified: 2009-12-30 17:54:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 3771 - Large images on image description pages are being sent original-size
Large images on image description pages are being sent original-size
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
All All
: Normal minor with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-10-21 16:49 UTC by David Benbennick
Modified: 2009-12-30 17:54 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description David Benbennick 2005-10-21 16:49:46 UTC
The image description page for [[Image:Map of Colorado highlighting Huerfano
County.png]], for example, shows the original 6711x4876 image, instead of a
thumbnail.  This gobbles bandwidth, and makes image description pages completely
unusable for those of use with limited computer memory.
Comment 1 Niklas Laxström 2005-10-21 16:56:13 UTC
[Wikitech-l] Images greater than 12.5 megapixels can't be thumbnailed
Comment 2 David Benbennick 2005-10-21 18:07:40 UTC
Ah, thanks!  I think that image description pages should still use the old
thumbnail link, even if the thumbnail won't get generated.  If the thumbnail
already exists, then the page will display fine.  And even if it doesn't, the
user can always click on the "download high resolution" link, but won't be
forced to download the huge image.

Note that this is what categories do, for example
Comment 3 Rowan Collins [IMSoP] 2005-10-21 21:06:03 UTC
Perhaps a special text link as a placeholder could be used, as in "This is a
very large image which can't be thumbnailed. Click here to view the full-size

But is the 12.5 megapixel thing really the problem here? By the looks of it,
these are SVGs, and should be thumbnailable really easily - the "S" stands for
"Scalable", after all. Oh, wait, you replaced them since reporting this bug. Any
chance of finding another example so we can see the behaviour in action?
Comment 4 David Benbennick 2005-10-21 21:24:19 UTC is
another example, which should stick around for at least a week or so (though
eventually I'll be converting those to SVG, too).

Text as placeholder sounds like a good idea.
Comment 5 David Benbennick 2005-10-21 21:29:49 UTC
Another problem with the current behavior is that, when a thumbnail of a large
image is used in an article, it appears as a red link.  So people come along and
remove the "deleted" image.  See
for example.  A blue link to the image description page would be much more useful.
Comment 6 Ævar Arnfjörð Bjarmason 2005-11-03 12:59:19 UTC
Not a critical issue, bumping to minor
Comment 7 wclark 2006-09-09 00:09:55 UTC
The original problem (large PNGs causing ImageMagick to eat up too much RAM) can
be fixed with a few command-line options:

I'll try to test this when I get a chance, to see if it really works as
advertised.  It would be nice if the size restriction could simply be lifted,
since this is the easiest solution to the related problems.
Comment 8 ravedave 2007-06-04 02:46:04 UTC
Still broken. Did you try out the parameters Bill Clark?
Comment 9 Guillaume Paumier 2009-12-30 17:54:37 UTC
AFAIK this doesn't happen any more; if the picture is too big, the thumbnail is replaced by an error message:
"Error creating thumbnail: Invalid thumbnail parameters or image file with more than 12.5 million pixels"

And there's an open bug about this specific issue ( bug 9497 ).

Note You need to log in before you can comment on or make changes to this bug.