Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Layout will not load #275

Open
GoogleCodeExporter opened this issue Nov 27, 2015 · 4 comments
Open

Layout will not load #275

GoogleCodeExporter opened this issue Nov 27, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link


I cannot open a saved layout.

My file included a large jpeg of the schematic on the layout to assist me.The 
saved diy file is about 65mb.

What is the expected output? What do you see instead?

The saved layout will not load. See attached log file. It will however open 
other layouts. I opened a new file and inserted the jpeg I mentioned above and 
saved it as a test file. I cannot open it and shows the same Java error 
messages .. out of memory.

3.28 Windows 8




Original issue reported on code.google.com by [email protected] on 5 May 2015 at 2:04

Attachments:

@GoogleCodeExporter
Copy link
Author

Issue 274 has been merged into this issue.

Original comment by [email protected] on 5 May 2015 at 6:36

@GoogleCodeExporter
Copy link
Author

Hi, I suggest increasing available memory to diylc. Open diylc.l4j.ini file and 
changing

-Xms512m -Xmx1024m -Dorg.diylc.scriptRun=true

into something like

-Xms512m -Xmx2048m -Dorg.diylc.scriptRun=true

if 2GB is not enough, try 3 or 4GB.

If none of that helps, try opening diy file in a text or html editor and just 
remove the tag that contains encoded image. You'll spot it easily, it's huge. 
Make sure you make a backup if you try this.

Original comment by [email protected] on 5 May 2015 at 6:40

@GoogleCodeExporter
Copy link
Author

Hi
Thanks for the prompt reply. Didn't follow your instructions carefully 
unfortunately.
Will have to start over. We live and learn.

Original comment by [email protected] on 5 May 2015 at 7:23

@GoogleCodeExporter
Copy link
Author

Gee, what did you do? :) Changing memory allocation is not destructive to the 
file.
Cheers

Original comment by [email protected] on 5 May 2015 at 8:35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant