FS#1001 refchecks when deleting media: php memory exhausted

UTF-8/Unicode

• 

  2006-12-13 jonb

  Exec summary
  ------------
  See http://forum.dokuwiki.org/post/1597
  Apparently
  "This is caused by the lookup for pages referencing the media file. It's the last bit of code which doesn't scale too well with big wikis."
  
  Whether mine is a big wiki, I don't know...
  # du -sm /home/wwwrnd/public_html/dokuwiki-2006-11-06/data/
  34      /home/wwwrnd/public_html/dokuwiki-2006-11-06/data/
  
  # find /home/wwwrnd/public_html/dokuwiki-2006-11-06/data/pages/ /home/wwwrnd/public_html/dokuwiki-2006-11-06/data/media/ -type f | wc -l
  145
  
  Original description:
  ---------------------
  When I try to delete a file (have tried 3, .jpg and .xls) via the media manager, the window goes blank, indicates "done", and stays blank - apparently hung.
  Looking in the apache error log, I see something like...
  
  [code]
  [client xx.xx.xx.xx] PHP Fatal error:  Allowed memory size of 16777216 bytes exhausted (tried to allocate 71 bytes) in /home/wwwrnd/public_html/dokuwiki-2006-11-06/inc/utf8.php on line 525, referer: https://my.pute.here/~wwwrnd/dokuwiki-2006-11-06/lib/exe/mediamanager.php?ns=wiki:some:namespace
  [/code]
  
  Am using dokuwiki 2006-11-06.
  This occurs for both firefox 2 on linux, and IE6 on windows.
  web server OS: linux RHEL 3.0
             apache: 2.0.52
                   php: 4.3.9
  
  I have already increased default php memory limit from 8M to 16M in /etc/php.ini.
  Do I just need to increase this again?
  (I did: to 32MB, and it still fails with same error "...Allowed memory size of 33554432 bytes exhausted (tried to allocate 71 bytes)...")
  
  Looking more closely at the php memory error, I see it occurs in the utf8.php file.
  
  So is it a font issue?
  
• 

  2006-12-13 andi

  Just an addition to my previous comment: you probably don't have the mb_string extension installed which means all UTF-8 handling needs to be done in pure PHP code which is slower and more memory intensive - which explains why you get this error even on a smaller wiki.
• 

  2006-12-14 jonb

  I'm not sure what to do about the mbstring extension!
  Firstly, since it is mentioned (all defaults) in /etc/php.ini, can I assume it is *is* installed?
  snippet from php.ini...
  
  [mbstring]
  
  ; language for internal character representation.
  ;mbstring.language = Japanese
  
  ; internal/script encoding.
  ; Some encoding cannot work as internal encoding.
  ; (e.g. SJIS, BIG5, ISO-2022-*)
  ;mbstring.internal_encoding = EUC-JP
  
  ; http input encoding.
  ;mbstring.http_input = auto
  
  ; http output encoding. mb_output_handler must be
  ; registered as output buffer to function
  ;mbstring.http_output = SJIS
  
  ; enable automatic encoding translation accoding to
  ; mbstring.internal_encoding setting. Input chars are
  ; converted to internal encoding by setting this to On.
  ; Note: Do _not_ use automatic encoding translation for
  ;       portable libs/applications.
  ;mbstring.encoding_translation = Off
  
  ; automatic encoding detection order.
  ; auto means
  ;mbstring.detect_order = auto
  
  ; substitute_character used when character cannot be converted
  ; one from another
  ;mbstring.substitute_character = none;
  
  ; overload(replace) single byte functions by mbstring functions.
  ; mail(), ereg(), etc are overloaded by mb_send_mail(), mb_ereg(),
  ; etc. Possible values are 0,1,2,4 or combination of them.
  ; For example, 7 for overload everything.
  ; 0: No overload
  ; 1: Overload mail() function
  ; 2: Overload str*() functions
  ; 4: Overload ereg*() functions
  ;mbstring.func_overload = 0
  
  ------------------------------------------------------------
  If I did change anythimg would it be something like this?
  
  mbstring.language             = English;
  mbstring.internal_encoding    = UTF-8  ;
  mbstring.encoding_translation = On;
  mbstring.http_input           = auto    ;
  mbstring.http_output          = pass    ;
  mbstring.detect_order         = auto    ;
  
  ------------------------------------------------------------
  One more thing, for what it's worth, the server is REHL 4, not 3 as stated above.
  
• 

  2006-12-14 andi

  You don't need to change any settings for the mbstring extension. It just needs to be installed. To check if it is available, please call doku.php?do=check on your server.
• 

  2006-12-14 jonb

  Thanks (and sorry if this is not the right forum for this discussion!)
  So doing that indicates that
   "mb_string extension not available - PHP only replacements will be used"
  
  Can you tell me how to install it?
  I'm still not clear if this is a php thing or a dokuwiki thing!!
  (I have tried to googling without finding anything obvious!)
  Are my suggested php.ini settings in previous comment correct?
  
  Thanks!
• 

  2006-12-14 andi

  You probably need to install the php-mbstring package (I think its called like this in RHEL) - if you have any further problems with installing or configuring please post in the forum.
• 

  2008-02-23 andi

  fixed with FS#1336
• Related tasks:
  • FS#1336 utf8 function times out when deleting media files if mbstring is not installed