Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350277 - Export Eclipse plugin application failed with permgem error (just simple plugin application)
Summary: Export Eclipse plugin application failed with permgem error (just simple plug...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-24 10:43 EDT by Tam Ho CLA
Modified: 2019-08-18 12:38 EDT (History)
4 users (show)

See Also:


Attachments
eclipse.ini (498 bytes, application/octet-stream)
2011-07-06 09:52 EDT, Tam Ho CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tam Ho CLA 2011-06-24 10:43:21 EDT
Build Identifier: Indigo officially

Export Eclipse plugin application failed with permgem error even try with simple plugin application

Reproducible: Always

Steps to Reproduce:
1. Create a plugin application (simple with a view)
2. Create a standard product, add splash screen
3. Perform export product
- Out of memory (pergem) is appeared even set to the maximum allow
Comment 1 Dani Megert CLA 2011-07-04 08:43:24 EDT
Are you sure you've set the permgen and not the heap memory?
Comment 2 Curtis Windatt CLA 2011-07-05 10:28:44 EDT
OOM exceptions have been seen during update site building (bug 350769) and product export.
Comment 3 Tam Ho CLA 2011-07-06 09:52:06 EDT
Created attachment 199185 [details]
eclipse.ini

Attached with the eclipse.ini file.
Comment 4 Tam Ho CLA 2011-07-06 09:54:19 EDT
I tried with RCP and Reporting bundle. This issue happens 95% with a small sample example. I will attach the example later if it's need.
Comment 5 Eclipse Genie CLA 2019-08-18 12:38:04 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.