Memory, Rendering and Java Options
DbSchema runs on the Java bundled with it. The options that this Java starts with, such as the memory limit and the graphics pipeline, are set in a text file in the installation folder:
| Operating system | File |
|---|---|
| Windows | DbSchema.vmoptions, next to DbSchema.exe |
| macOS | DbSchema.app/Contents/vmoptions.txt |
| Linux | DbSchema.vmoptions, next to the DbSchema launcher |
The file holds one option per line, and a line starting with # is ignored. Close DbSchema before editing the file, and start it again for the change to take effect.
Memory
The -Xmx line sets the most memory that DbSchema may use, for example -Xmx8G for 8 GB. If DbSchema reports that it ran out of memory, which happens with very large schemas or diagrams, raise the value, keeping it below the memory of the computer.
Slow Painting, Freezes and Remote Desktop
DbSchema draws with the graphics card. Over Windows Remote Desktop, in some virtual machines, and with some graphics drivers, that makes painting slow, makes tooltips flicker, or freezes the window after it sat idle. When DbSchema notices slow painting, it shows a Slow Rendering Detected notification.
The file already holds the lines that switch to software rendering. Remove the # in front of them:
-Dprism.order=sw
-Dprism.vsync=false
Log Files for a Support Ticket
DbSchema writes its log to .DbSchema/logs/logs.txt in your home folder. To read it, open Help → Output Logs. To attach it to a ticket, open Help → Report a Bug and click Show files, which opens the folder.