-
Bug
-
Resolution: Fixed
-
Low
-
5.4.4, 5.6.3, 5.7
-
Confluence 5.4.4, 5.6.3
-
8
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Summary
Slowness Rendering a Page with the 'Section' Macro
Steps to Reproduce
- Create a Page
- Select the 'Edit' option from the top right menu
- type ‘{section’ to bring up the section macro and select it
- Enter information in the ‘Section’ macro. (I saw the degradation grow as multiple items were added, but over 100 items is very noticeable)
- Save the page (should be slow)
- Navigate away and back to the page (should be slow)
If the same information is entered on a page without the section macro, it renders without speed degradation.
Expected Result
The page would render normally and not take a noticeable amount of time to do so
Actual Result
- The page takes a noticeable amount of time to render
- In Confluence Cloud any text that does not render within a section column within 60 seconds will be truncated from the page (Location of text is random within document)
- Effects are compounded if using firefox with FireBug enabled
Environment
Confluence 5.4.4
Other Notes
- I have attached a Storage format of a page that has many items (so that it is easier to recreate by adding through source editor)
- If you remove the data from the Section macro, the page renders very quickly. That is reason for submitting this as a bug as it seems to be an issue with the ‘Section’ Macro itself
- Only tested on Confluence 5.4.4 and 5.6.3. Issue is present in both.
- causes
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned in
-
Page Loading...
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
(1 mentioned in)
[CONFSERVER-35285] Slowness Rendering a Page with the 'Section' Macro
| Workflow | Original: JAC Bug Workflow v3 [ 2876219 ] | New: CONFSERVER Bug Workflow v4 [ 3005266 ] |
| Workflow | Original: JAC Bug Workflow v2 [ 2803846 ] | New: JAC Bug Workflow v3 [ 2876219 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JAC Bug Workflow [ 2737907 ] | New: JAC Bug Workflow v2 [ 2803846 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2401322 ] | New: JAC Bug Workflow [ 2737907 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2301440 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2401322 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2235219 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2301440 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2198437 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2235219 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1941668 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2198437 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1731596 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1941668 ] |
| Description |
Original:
h2. Summary
Slowness Rendering a Page with the 'Section' Macro h2. Steps to Reproduce # Create a Page # Select the 'Edit' option from the top right menu # type ‘{section’ to bring up the section macro and select it # Enter information in the ‘Section’ macro. (I saw the degradation grow as multiple items were added, but over 100 items is very noticeable) # Save the page (should be slow) # Navigate away and back to the page (should be slow) *If the same information is entered on a page without the section macro, it renders without speed degradation.* h2. Expected Result The page would render normally and not take a noticeable amount of time to do so h2. Actual Result - The page takes a noticeable amount of time to render - In Confluence Cloud any text that does not render within a section column within 60 seconds will be truncated from the page (Location of text is random within document) -- Effects are compounded if using firefox with FireBug enabled h2. Environment Confluence 5.4.4 h2. Other Notes * I have attached a Storage format of a page that has many items (so that it is easier to recreate by adding through source editor) * If you remove the data from the Section macro, the page renders very quickly. That is reason for submitting this as a bug as it seems to be an issue with the ‘Section’ Macro itself * Only tested on Confluence 5.4.4 and 5.6.3. Issue is present in both. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-35285]. {panel} h2. Summary Slowness Rendering a Page with the 'Section' Macro h2. Steps to Reproduce # Create a Page # Select the 'Edit' option from the top right menu # type ‘{section’ to bring up the section macro and select it # Enter information in the ‘Section’ macro. (I saw the degradation grow as multiple items were added, but over 100 items is very noticeable) # Save the page (should be slow) # Navigate away and back to the page (should be slow) *If the same information is entered on a page without the section macro, it renders without speed degradation.* h2. Expected Result The page would render normally and not take a noticeable amount of time to do so h2. Actual Result - The page takes a noticeable amount of time to render - In Confluence Cloud any text that does not render within a section column within 60 seconds will be truncated from the page (Location of text is random within document) -- Effects are compounded if using firefox with FireBug enabled h2. Environment Confluence 5.4.4 h2. Other Notes * I have attached a Storage format of a page that has many items (so that it is easier to recreate by adding through source editor) * If you remove the data from the Section macro, the page renders very quickly. That is reason for submitting this as a bug as it seems to be an issue with the ‘Section’ Macro itself * Only tested on Confluence 5.4.4 and 5.6.3. Issue is present in both. |