If you don't know whether you have 32-bit or 64-bit Linux,
use the command
64 is in the output,
you have 64-bit Linux;
otherwise, you have 32-bit Linux.
Almost all Mac OS X systems have a 64-bit OS, so we recommend using the 64-bit Dart Editor. If you encounter problems, try the 32-bit version.
If you don't know whether you have 32-bit or 64-bit Windows, see Microsoft's support site.
Your Java version should have the same bit width as your Dart Editor version. For example, if you're using a 64-bit Dart Editor, then you should use 64-bit Java. Otherwise, you might see a message like this when you try to launch Dart Editor:
Failed to load the JNI shared library "C:\Program Files(x86)\Java\jre6\\bin\client\jvm.dll
To determine which version of Java you are running, do one of the following:
If you're using 64-bit Linux but have 32-bit Java libraries, Dart Editor won't work.
The fix: Use a 64-bit Java JDK. You can get a 64-bit JDK 7 from Java SE Development Kit 7 Downloads. If you already have a 64-bit JDK but it's not the default, you can specify the Java runtime.
A few things can go wrong when launching Dart Editor on a Mac:
If you're running Mac OS 10.8 (Mountain Lion), your computer might refuse to start Dart Editor because it's not from the Mac App Store or an identified developer. Until we fix this problem (bug #5088), you can work around it.
The easiest workaround: When launching Dart Editor for the first time, don't double-click the Dart Editor icon. Instead, right-click (or Ctl+click) it to bring up a context menu, and choose Open. Then, in the dialog that comes up, click Open.
An alternative workaround is to change your security settings. Go to System Preferences > Security & Privacy. In the General tab under Allow applications downloaded from:, choose Anywhere. You should now be able to start Dart Editor. Once you've run Dart Editor, you can change the preference back to its previous setting.
Sometimes when you try to launch a new, 64-bit build of Dart Editor, Mac OS X incorrectly displays a corruption warning:
"DartEditor.app" is damaged and can't be opened. You should move it to the Trash.
The workaround is to download and install the 32-bit version of Dart Editor.
When you try to run Dart Editor but don't have a Java SE 6 runtime, Dart Editor offers to install Java for you. If the installation doesn't work, you can either restart Dart Editor or install Java yourself.
If you use Sophos Anti-Virus, Dart Editor (like most Java applications) starts up 10-15 times slower than normal.
The fix: Turn off scanning of the app's JAR files. For example:
.jarfiles, and click Open.
If you're using one of the increasingly rare 32-bit Macs, you can't launch the 64-bit version of Dart Editor. Instead, you see a warning like this:
The fix: Download and install the 32-bit version of Dart Editor.
If necessary, you can specify the Java runtime that Dart Editor uses.
Go to your Dart installation directory and
add the following two lines to
immediately before the existing
On Windows, use double backslashes (
as the directory separator:
DartEditor.ini might have:
... -vm /usr/local/buildtools/java/jdk-64/bin/java -vmargs ...
When building larger Dart applications, Dart Editor needs more
memory for analysis. If you are not already using 64-bit,
switch to a 64-bit Java Virtual Machine (JVM),
and to the 64-bit version of Dart Editor.
In the DartEditor.ini file, find the
and change it to
-Xmx2000m, or larger if you have more RAM
Java 7 sports different garbage collection (GC) behavior than Java 6.
If you see large pauses when editing files, and you have addressed
the memory issues, edit the
DartEditor.ini file, and insert a line after
-vmargs that contains the string
In extremely rare cases, a Dart Editor crash will corrupt the workspace data on disk, preventing Dart Editor from restarting. The workaround is to delete the Dart Editor workspace directory (see Clearing all settings) and then Dart Editor will be able to restart.
That directory contains workspace and preference state information, so if you have changed any Dart Editor preferences, you will need to change those preferences again when you delete that folder and restart Dart Editor.
By default, when you click Dart Editor's Run button , your web app runs in Dartium. If you instead see a message that you need to download a new version of Dartium, your software is old.
The fix: Download and install a new version of Dart Editor. You'll get an updated version of Dartium, plus the latest improvements to Dart Editor. Alternatively, download a new version of Dartium and substitute it for the copy that's in your Dart installation directory.
If you're experiencing the error
libudev.so.0: cannot open shared object file: No such file or directory
on Dartium startup, the resolution in issue 12325
may be of help.
If Dart Editor and Eclipse
share the same
they'll save conflicting settings,
resulting in warnings and errors from both
Dart Editor and Eclipse.
The fix: Don't use the same workspace for Dart Editor and any other Eclipse-based software.
pub get behind a proxy,
you may see
socket (connection) errors when the command attempts to pull
down dependencies from an external website, such as pub.dartlang.org.
You can fix this by setting the environment variables
no_proxy. In the following examples,
9090 with the appropriate
port for your proxy:
http_proxy=http://<yourproxy>.<yourdomain>.com:9090/ https_proxy=https://<yourproxy>.<yourdomain>.com:9090/ no_proxy=localhost,127.0.0.1If your proxy needs authentication, the setup will look more like the following:
To enable Dart Editor to check for updates, add the following to the
-Dhttp.proxyHost=<yourproxy>.<yourdomain>.com -Dhttp.proxyPort=9090 -Dhttps.proxyHost=<yourproxy>.<yourdomain>.com -Dhttps.proxyPort=9090
If you need a user name and password for authentication, add:
-Dhttp.proxyUser=<username> -Dhttp.proxyPassword=<passwordstring> -Dhttps.proxyUser=<username> -Dhttps.proxyPassword=<passwordstring>
Dart Editor settings are in a platform-dependent directory, so you don't lose them when you update Dart Editor. If your settings become corrupted or you want to see the new user experience, delete the settings directory.
The following table shows where Dart Editor settings are saved.
|Platform||Location of settings|
To aid in debugging Dart Editor performance issues, you can generate a heap dump.
For Linux or Mac users:
Use top to get the pid of Dart Editor. Then, run
If the given process is running on a 64-bit VM, you may need to
Please attach the output
to the relevant bug at dartbug.com.
More information on jstack is available.
Dart Editor sometimes adds experimental support for new features, requiring you to explicitly request support for the new feature.
To enable support for a new feature, go to Preferences, and click Experimental. Here is a partial list of what you might want to do:
Under some circumstances, network storage can prevent Dart Editor form creating new projects (see issue 9238). The workaround is to modify your DartEditor.ini file, changing the following entry:
$user.home\DartEditorTo something like the following:
Some of the more common problems on Linux include:
Dart Editor issues lists all of the known bugs in Dart Editor.
Click an issue's star to receive updates about it. You can also file new issues and add comments to existing ones.