Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337880 - Performance: It takes about 30 minutes to start RSA 802 the first time it's launched by a non-admin user
Summary: Performance: It takes about 30 minutes to start RSA 802 the first time it's ...
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-22 13:42 EST by Allen Zhou CLA
Modified: 2011-02-23 11:19 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Allen Zhou CLA 2011-02-22 13:42:31 EST
Build Identifier: IES 362

If you upgrade RSA to 8.0.2 as admin, it takes about 30 min to start RSA 802 the first time you launch the product as non-admin user
Note that I'm using a WinXP SP3 image with 2.5 GB of memory

Steps:

Did a full install of RSA 8.0 as admin using IM 1.4.1
Launched RSA 8.0 as admin and created a modeling project.
Logged off and launched RSA 8.0 as non-admin and created a modeling project.
Logged in as admin and upgraded IM to 1.4.3
Upgraded RSA to 8.0.2 and picked all the new features
Launched RSA 8.0.2  as admin and edited the model.
Logged off and launched RSA 8.0.2 as non-admin

Results:
It took about 30 minutes to start the product.
Note that when the product launched there were errors in the log that might be related to the slow start.
See attached log.

Subsequent launch of the product are fine it's only the first one that took very long.



Reproducible: Always

Steps to Reproduce:
1.Did a full install of RSA 8.0 as admin using IM 1.4.1
2.upgraded to RSA 8.0.2 using IM 1.4.3
3.start product as non-admin user
Comment 1 Prakash Rangaraj CLA 2011-02-22 22:59:39 EST
Please raise a bug against RSA. Or if you find any specific component in Eclipse causes this, please reopen with details.