Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-25262

Memory leak in dashboard widget "Item history"

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Duplicate
    • Icon: Trivial Trivial
    • None
    • 7.0.3
    • Frontend (F)
    • None
    • Zabbix 7.0.3 on RHEL 9.4

      Steps to reproduce:

      1. Create new dashboard with "Item history" widget, try to add column with some Item value

      Result:
      The widget shows red error message "Internal server error" and do not save.

      The /var/log/httpd/error_log contains:

      [Wed Sep 18 10:12:15.683246 2024] [proxy_fcgi:error] [pid 406819:tid 406904] [client 10.251.43.145:27320] AH01071: Got error 'PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /usr/share/zabbix/include/classes/api/CRelationMap.php on line 43PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /usr/share/zabbix/include/func.inc.php on line 1181PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /usr/share/zabbix/include/classes/core/CEncryptedCookieSession.php on line 68PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /usr/share/zabbix/include/classes/debug/CProfiler.php on line 338', referer: https://zabbix.domain.com/zabbix/zabbix.php?action=dashboard.view&dashboardid=177 

      Even set PHP memory limit in /etc/php-fpm.d/zabbix.conf  to 256M is not enough, after setting 512M it starts working. But the save of the widget is very slow.

       

      Workaround:
      Set PHP memory limit to 512M

      Expected:
      The widget works with default zabbix PHP memory limit 128MB.

            zabbix.dev Zabbix Development Team
            kbelunek Karel Bělunek
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: