Designer 5.2 crashes on Windows 10

[Segi]

Ever since I updated to the latest version of Ebase, I've noticed that Designer will stop responding and get the blue spinning wheel of death in Windows 10 and I have to force close it. This just happened to me and I checked the memory usage of designer before it force closed which was at 883MB. I only had 5 scripts/forms open in Designer when this happened.

On other occasions, designer doesn't crash but seems really sluggish and slow to open forms. When I check the Windows task manager, designer.exe is at ~ 1.8-2.3GB of RAM usage.

[Jon]

That's a lot of memory! What do you have your max Java memory set to on the designer?

Do you have anything in the designer log file in UfsClient/logs?

Are you using standard Windows 10?

Which Java version?

Are you using the integrated server? If yes, what is its max memory set at?

[Segi]

Jon,

1. Where do I check the max Java memory for designer ? I launch the designer directly from designer.exe

2. Windows 10 Pro

3. Java version is 1.8.0_60

4. No. This is occurring on a development environment where I do my work and deploy it to the server.

[Jon]

The memory is set in the designer.vmoptions file when using the exe - it's set to 1Gb by default so I guess that's what you have. Anything in your designer logs?

[Segi]

Jon,

The file designer.vmoptions doesn't have a max memory option specified so it must use the default.

The client logs don't have any entries from today. The last entry is from a month ago

[Segi]

Jon,

I just realized that I made a little mistake in what I previously told you because I had opened the designer.vmoptions on the server instead of my workstation. The designer.vmoptions on my workstation DOES have this line: -Xmx512m so its set to 512MB max. memory. Should I increase this to 1024 ? I don't remember ever explicitly setting this when I installed designer on my workstation so I want to say that that's the default.

[Jon]

1024 is a good number. But this doesn't explain why your system was appearing to use much more memory. You might try rebuilding the data dictionary (from the View menu) to see if that helps.

[Segi]

Thanks,

I'll try that and see if it helps

[Segi]

just an update:

I rebuilt the data dictionary and changed the max memory size to 1024KB. As of right now, the memory usage for the designer is 1.2GB which is above the max limit

[geadon]

Just for info, I am running the designer on windows 7 and designer.exe is using over 1Gb or memory. It rarely crashes (unless I go to change the property set of a control that has a missing property set). My machine does have 16GB or RAM though.