Skip to main content

 –

Troubleshooting long-lived clipboard pages

Suggest edit Updated on November 29, 2021

Clipboard pages that remain unused for long periods could indicate a design or implementation flaw that can hurt performance. For example, the application created a page but neglected to use the Page-Remove method to remove the page after it was no longer needed.

When building or testing an application, you can discover whether your own processing has created such "orphan" or "near-orphan" page.
  1. Select Clipboard from the developer toolbar in Dev Studio.
  2. Once the clipboard is open, select ToolsAnalyze.
  3. In the resulting grid of data, look in the Est Size (KB), Last Passivation, and Last Activation columns to identify any pages that were automatically passivated but never reactivated.
  4. Research whether such pages are needed at all, and whether they can be removed at specific points in the application, to reduce clipboard size.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us