Skip to main content
C
CraigSenovich1-Visitor
1-Visitor
October 1, 2015
Question

CreoView Memory Usage

  • October 1, 2015
  • 4 replies
  • 3580 views

We have suddenly encountered a problem company wide where when doing certain actions in CreoView, like selecting File/Options causes CreoView to utilize all CPU Physical Memory and causes the CPU to become unresponsive for several minutes.   This just started happening where it was fine before.  Any suggestions?

CreoView 3.0

4 replies

B
BillRyan16-Pearl
16-Pearl
October 1, 2015


I would eliminate the settings files as a possible issue...there are three of them that can get loaded.(server, install dir, user directory)  If you have Cache enabled...you may want to clear it.

Capture.JPG

C
CraigSenovich1-VisitorAuthor
1-Visitor
October 13, 2015

Still no resolution on this, clearing Cache did not have any affect. deleting settings files also had no affect. 

B
BillRyan16-Pearl
16-Pearl
October 13, 2015

I'd say it is time to write a case...I'm pretty sure they will be asking for you to turn on logging and then you can send them the informaiton.  Logging is fairly easy in Creo view with a couple additions to the environment variables. 

A
AnandKumar1-Visitor
1-Visitor
October 14, 2015

When issues happens like this,easiest way is to uninstall creo view ,restart the system & reinstall back freshly. This would resolve the issue.......

C
CraigSenovich1-VisitorAuthor
1-Visitor
October 14, 2015

Finally discovered the issue.

The xml file for server preferences in the Visualization Configuration Administration at the site level was very large.  Removing unnecessary properties and reducing the file size fixed the issue.    Users must also clear the browser and creoview cache.

B
BillRyan16-Pearl
16-Pearl
October 14, 2015

check out SPR 4591120 which talks about preference file size.  You may also want to watch out for the size of the user_prefs file.  I'd be interested to know what type of information was being stored in the server side preference file that caused the file size increase.  What we found in the user preference file was the branch link information...which I believe yields better performance for finding the location of the metadata on the server.

Terms & ConditionsCookie settingsAccessibility statement