Last modified: 2014-08-19 17:23:05 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 3862 - Progressive JPEGs break Image page
Progressive JPEGs break Image page
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
1.5.x
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://arcanologia.ru/wiki/Image:Gomf...
:
: 69377 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-11-02 21:00 UTC by Mike Stukalov
Modified: 2014-08-19 17:23 UTC (History)
2 users (show)

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


Attachments

Description Mike Stukalov 2005-11-02 21:00:41 UTC
When I upload progressive JPEG, the Image page for this file is not showing up -
Firefox just doesn't seem to follow link and IE throws "cannot find server"
error (for whatever reason).

However, if I save the same image in non-progressive JPEG, it is displayed
perfectly.

Links:
Progressive JPEG: http://arcanologia.ru/wiki/Image:Gomfirst.jpg ;
http://arcanologia.ru/images/0/07/Gomfirst.jpg
Non-progressive: http://arcanologia.ru/wiki/Image:Gom1.jpg ;
http://arcanologia.ru/images/0/0e/Gom1.jpg
Comment 1 Mike Stukalov 2005-11-02 21:24:58 UTC
Apparently the progressive/non-progressive isn't the cause here.
Here's what I'm seeing in log file:
[Thu Nov 3 00:20:10 2005] [error] PHP Fatal error: Allowed memory size of
8388608 bytes exhausted (tried to allocate 1312 bytes) in
/home/u29958/arcanologia.ru/www/includes/Image.php on line 1073

Now the question is - what for does it need 8M to display an image?! Does
reading it's parameters eat so much memory?
Comment 2 Ævar Arnfjörð Bjarmason 2005-11-02 21:27:35 UTC
Resolving as INVALID, a php memory configuration problem and not a MediaWiki issue.
Comment 3 Bawolff (Brian Wolff) 2014-08-19 17:23:05 UTC
*** Bug 69377 has been marked as a duplicate of this bug. ***

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


Navigation
Links