0017955: Blank changelog page when size of changelog exceeds a certain threshold - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0017955	mantisbt	change log	public	2014-12-12 06:08	2015-01-02 13:13

Reporter	jensberke	Assigned To	dregad
Priority	high	Severity	major	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	1.2.18

Summary	0017955: Blank changelog page when size of changelog exceeds a certain threshold
Description	The changelog page is rendered completely blank (contains no HTML code at all) when the size of changelog exceeds a certain threshold. I haven't figured out what that threshold exactly is, but it must be either the number of versions, the number of tickets or maybe simply the size of the changelog page that was going to be rendered. Or it's a combination of these. Two concrete examples from our data: A changelog for a project with 33 versions and 772 tickets altogether will be a blank page. A changelog for a project with 8 versions and 12 tickets altogether will be rendered correctly. This must have been introduced in 1.2.18 because the problem doesn't exist in 1.2.17
Steps To Reproduce	Have a lot of versions and/or tickets in a project (threshold not known so far) Set the "project" filter either to "all" or to that project Click on "changelog" => blank page
Tags	No tags attached.

dregad 2014-12-12 08:55 developer ~0042004	Are there any errors (e.g. out of memory) in your server logs ? On this tracker, the changelog for mantisbt project contains 71 versions / nearly 3000 issues, and loads in about 7-8 seconds. I don't get any errors for "All projects" either. As I'm not able to reproduce the problem, it would be helpful if you could trace the error in changelog_page.php, or even better (if you know how to do it) identify the commit that introduced the regression using git bisect.

jensberke 2014-12-12 10:32 reporter ~0042005	You're right, it's a memory issue. The server error log contains the following errors (I should have looked there beforehand): Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 368641 bytes) in /home/username/mantis-1.2.18/core/custom_function_api.php on line 59 Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 389121 bytes) in /home/username/mantis-1.2.18/changelog_page.php on line 303 So there must have been an increase in memory consumption between 1.2.17 and 1.2.18 which we should be able to circumvent by adding/allowing more memory to our server. I think the ticket can be closed. Sorry for the inconvenience.

dregad 2014-12-12 10:44 developer ~0042006	Thanks for feedback. If you find out what is causing the increased memory usage, let us know.