My old XP system needed upgrading - basically because Oxygen was very slow. Yesterday I bought a new desktop computer with 3 Gigabytes of memory and was looking forward to fast transformations |-)! I installed Oxygen and everything looked great. I tried running a transformation that takes 2 seconds on my old XP with 512 megabytes of memory and the transformation took 5 minutes. I tried it again and got a message saying to increate the "-Xmx" in Oxygen.bat. I increased it from 256m to 512m then to 1g and am still having the same problem. I couldn't find any information on the archives. Anyone have any advice on solving this problem. TIA! Betty /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Betty Harvey | Phone: 410-787-9200 FAX: 9830 Electronic Commerce Connection, Inc. | harvey@eccnet.com | Washington,DC XML Users Grp URL: http://www.eccnet.com | http://www.eccnet.com/xmlug /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Pray for Mac (http://www.macsteam.org)
Run your transform with saxon ... without oxygen ... this is not likely oxygen ... just a guess ... harvey wrote:
My old XP system needed upgrading - basically because Oxygen was very slow. Yesterday I bought a new desktop computer with 3 Gigabytes of memory and was looking forward to fast transformations |-)!
I installed Oxygen and everything looked great. I tried running a transformation that takes 2 seconds on my old XP with 512 megabytes of memory and the transformation took 5 minutes. I tried it again and got a message saying to increate the "-Xmx" in Oxygen.bat.
I increased it from 256m to 512m then to 1g and am still having the same problem.
I couldn't find any information on the archives. Anyone have any advice on solving this problem.
TIA!
Betty
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Betty Harvey | Phone: 410-787-9200 FAX: 9830 Electronic Commerce Connection, Inc. | harvey@eccnet.com | Washington,DC XML Users Grp URL: http://www.eccnet.com | http://www.eccnet.com/xmlug /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Pray for Mac (http://www.macsteam.org) _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Duh! Sometimes I forget to look at the obvious! I was having other issues with Vista and didn't even think to look at the result file because of the crashing. I had made one change to the XSLT when migrating from XP to Vista but it was enough to create a 77 MB file and cause Oxygen to crash when trying to open it! I really hate upgrading to new computers just because of the sheer work getting programs installed and working. Oxygen is one of my favorite programs and it was one of the ones I was concerned about but all is working fine! Thsnks! Betty
Run your transform with saxon ... without oxygen ... this is not likely oxygen ... just a guess ...
harvey wrote:
My old XP system needed upgrading - basically because Oxygen was very slow. Yesterday I bought a new desktop computer with 3 Gigabytes of memory and was looking forward to fast transformations |-)!
I installed Oxygen and everything looked great. I tried running a transformation that takes 2 seconds on my old XP with 512 megabytes of memory and the transformation took 5 minutes. I tried it again and got a message saying to increate the "-Xmx" in Oxygen.bat.
I increased it from 256m to 512m then to 1g and am still having the same problem.
I couldn't find any information on the archives. Anyone have any advice on solving this problem.
TIA!
Betty
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Betty Harvey | Phone: 410-787-9200 FAX: 9830 Electronic Commerce Connection, Inc. | harvey@eccnet.com | Washington,DC XML Users Grp URL: http://www.eccnet.com | http://www.eccnet.com/xmlug /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Pray for Mac (http://www.macsteam.org) _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hello, Generally you should not try to open files larger than 70 MB in oXygen. In such cases the total memory needed for the Java virtual machine may exceed the maximum limit allowed for Windows processes, that is 2 GB (if 4 GB tuning is not enabled in Windows) which ends up with a crash of the JVM. Regards, Sorin harvey wrote:
I had made one change to the XSLT when migrating from XP to Vista but it was enough to create a 77 MB file and cause Oxygen to crash when trying to open it!
One more remark: however files up to 2 GB in size can be opened in read-only mode in the Large File Viewer tool available from the Tools menu and also available as a standalone tool from the group of oXygen shortcuts on the Start menu. Regards, Sorin Sorin Ristache wrote:
Hello,
Generally you should not try to open files larger than 70 MB in oXygen. In such cases the total memory needed for the Java virtual machine may exceed the maximum limit allowed for Windows processes, that is 2 GB (if 4 GB tuning is not enabled in Windows) which ends up with a crash of the JVM.
Regards, Sorin
harvey wrote:
I had made one change to the XSLT when migrating from XP to Vista but it was enough to create a 77 MB file and cause Oxygen to crash when trying to open it!
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
On Fri, 2007-11-02 at 11:14 +0200, Sorin Ristache wrote:
Hello,
Generally you should not try to open files larger than 70 MB in oXygen. In such cases the total memory needed for the Java virtual machine may exceed the maximum limit allowed for Windows processes, that is 2 GB (if 4 GB tuning is not enabled in Windows) which ends up with a crash of the JVM.
Hi Sorin, I edit larger XML files (100~150MB) in a Java application that uses Xerces parser without memory problems. The maximum memory allowed parameter is set to almost 1GB (-Xmx999M). What parser does oXygen use? Regards, Rodolfo -- Rodolfo M. Raya <rmraya@maxprograms.com>
Hello Rodolfo, The cause of the very large memory amount needed for opening large documents is the architecture of the Java Swing components needed for rendering a document in the syntax highlighted _text editor_. It is an inherent problem of the Swing architecture which has no connection with the parser. Regards, Sorin Rodolfo M. Raya wrote:
On Fri, 2007-11-02 at 11:14 +0200, Sorin Ristache wrote:
Hello,
Generally you should not try to open files larger than 70 MB in oXygen. In such cases the total memory needed for the Java virtual machine may exceed the maximum limit allowed for Windows processes, that is 2 GB (if 4 GB tuning is not enabled in Windows) which ends up with a crash of the JVM.
Hi Sorin,
I edit larger XML files (100~150MB) in a Java application that uses Xerces parser without memory problems. The maximum memory allowed parameter is set to almost 1GB (-Xmx999M). What parser does oXygen use?
Regards, Rodolfo
On Fri, 2007-11-02 at 12:13 +0200, Sorin Ristache wrote:
Hello Rodolfo,
The cause of the very large memory amount needed for opening large documents is the architecture of the Java Swing components needed for rendering a document in the syntax highlighted _text editor_. It is an inherent problem of the Swing architecture which has no connection with the parser.
My app uses SWT, not Swing. That may explain the difference. Rodolfo -- Rodolfo M. Raya <rmraya@maxprograms.com>
participants (4)
-
harvey -
James Don -
Rodolfo M. Raya -
Sorin Ristache