Page MenuHomePhabricator

Entering Croatian characters produces errors
Closed, ResolvedPublic

Description

Author: radoslav.dejanovic

Description:
The system is set up to use UTF-8. The system is fine as long as there's no Croatian characters; entering any Cro character (č,ć,ž,š,đ) causes error messages such as this:

Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 64 bytes) in /var/www/includes/SpecialPage.php on line 160

The amount of bytes varies from 64 bytes to several kilobytes, and affected are SpecialPage.php (line 160), SiteStats.php (171), UserMailer.php (195). Despite the error message, the data is accepted and once I refresh the page, I can see the whole text, together with Croatian characters in it. Trying to edit the page again causes the same error message and changes to the data are accepted. Therefore, it is possible to insert Croatian characters into Wiki, but not without producing error messages.


Version: 1.13.x
Severity: major
OS: Linux
Platform: PC

Details

Reference
bz15058

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:20 PM
bzimport set Reference to bz15058.
bzimport added a subscriber: Unknown Object (MLST).

The presence of non-ASCII characters in input triggers loading of Unicode normalization data; it looks like the 20mb memory limit is getting hit here; this shouldn't really be hitting the limit, but if you have enough other things loaded that may be legit. :(

Try raising the limit from 20; this may be set in your php.ini or in LocalSettings.php (in response to an even lower default limit).

radoslav.dejanovic wrote:

I have done that - increased memory limit to 64MB in php.ini, but the error persists. I will check again on a different computer in a few days and report.

If the 20 mb error persists, *update LocalSettings.php*.

Assumed fixed, lacking response.

radoslav.dejanovic wrote:

Psst... regarding lack of response, take a look at this:

http://en.wikipedia.org/wiki/Vacation

:-)

Anyway, I have tried it today and I do confirm that increasing memory limit in LocalSettings.php does fix the issue.