-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
5.4.3, 5.6.3, 5.7.4, 5.9.11, 5.8.17, 6.3.4, 6.4.0, 6.6.0, 6.10.0, 6.15.1, 6.15.2, 7.4.0
-
13
-
Severity 2 - Major
-
3
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
We recently upgraded from Confluence 5.1.4 to 5.4.3 and now some of our more complex pages and templates are broken. We've isolated the issue down to the number of sub-nested macros. To recreate the issue do the following:
Create a page with 35 Info macros on after another = no problem
Create a page with 35 info macros continually nested inside of each other and the page will timeout after 2 minutes trying to save. (Page not found error).
I chose the info macro because it is a very basic Atlassian macro however I've reproduced this with a variety of different macros.
- relates to
-
-
- Closed
-
- mentioned in
-
Page Loading...
[CONFSERVER-35359] Too many nested macros break page
Ethan Foulkes
added a comment - We are in the graveyard =( I have big performance issues due to this. Each time Ethan comments I get notified too and get reminded that I too would really like a solution and get reminded that Atlassian sucks at listening (or evening responding) to these kind of issues.
Ethan Foulkes
added a comment - Hope this can be considered! Ethan Foulkes
added a comment - Skipped a month =)
Bump! Ethan Foulkes
added a comment - Bumpppppppppppppppppppppppp I really have performance issues due to this! Please respond!
Ethan Foulkes
added a comment - Have noticed some some other performance related issues around macros even when not nested in multiple layers. For example a macro with 8 macros nested at level 2 that can be recreated by using a single HTML macro with straight code inside of it renders much faster.
Does Atlassian just not really care about macro performance because they are typically used so lightly? I wouldn't be thrilled but would be OK with that if it's the truth...
Ethan Foulkes
added a comment - Have noticed some some other performance related issues around macros even when not nested in multiple layers. For example a macro with 8 macros nested at level 2 that can be recreated by using a single HTML macro with straight code inside of it renders much faster.
Does Atlassian just not really care about macro performance because they are typically used so lightly? I wouldn't be thrilled but would be OK with that if it's the truth... Ethan Foulkes
added a comment - Bump. Still here....ugh. 
After creating a case with Atlassian this bug fits our problem. Can this be solved for future releases.
We are running confluence Server 6.4 and saw this problem while using collaborative editing.