<p dir="auto">Tested with Firefox last stable &amp; developer edition (Aurora).<br>
If i open a new tab or one with content, and i drag it away (to open a new window), and move the cursor over Atom it closes.</p>
<p dir="auto">Here the shell output:</p>
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="mfkinder@wk-boe001:~$ atom
mfkinder@wk-boe001:~$ [14953:0213/170206:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[14983:0213/170206:INFO:renderer_main.cc(211)] Renderer process started
App load time: 314ms
[14953:0213/170208:INFO:CONSOLE(11)] &quot;activate linter-jshint&quot;, source: /home/mfkinder/.atom/packages/linter-jshint/lib/init.coffee (11)
[14953:0213/170208:INFO:CONSOLE(79)] &quot;Window load time: 1688ms&quot;, source: file:///usr/share/atom/resources/app/static/index.js (79)
The program 'atom' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 495 error_code 5 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)"><pre class="notranslate">mfkinder@wk-boe001:<span class="pl-k">~</span>$ atom
mfkinder@wk-boe001:<span class="pl-k">~</span>$ [14953:0213/170206:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox<span class="pl-k">!</span> See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment <span class="pl-k">for</span> more information on developing with the sandbox on.
[14983:0213/170206:INFO:renderer_main.cc(211)] Renderer process started
App load time: 314ms
[14953:0213/170208:INFO:CONSOLE(11)] <span class="pl-s"><span class="pl-pds">"</span>activate linter-jshint<span class="pl-pds">"</span></span>, source: /home/mfkinder/.atom/packages/linter-jshint/lib/init.coffee (11)
[14953:0213/170208:INFO:CONSOLE(79)] <span class="pl-s"><span class="pl-pds">"</span>Window load time: 1688ms<span class="pl-pds">"</span></span>, source: file:///usr/share/atom/resources/app/static/index.js (79)
The program <span class="pl-s"><span class="pl-pds">'</span>atom<span class="pl-pds">'</span></span> received an X Window System error.
This probably reflects a bug <span class="pl-k">in</span> the program.
The error was <span class="pl-s"><span class="pl-pds">'</span>BadAtom (invalid Atom parameter)<span class="pl-pds">'</span></span>.
  (Details: serial 495 error_code 5 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously<span class="pl-k">;</span>
   that is, you will receive the error a <span class="pl-k">while</span> after causing it.
   To debug your program, run it with the --sync <span class="pl-c1">command</span> line
   option to change this behavior. You can <span class="pl-k">then</span> get a meaningful
   backtrace from your debugger <span class="pl-k">if</span> you <span class="pl-c1">break</span> on the <span class="pl-en">gdk_x_error</span>() function.)</pre></div>
<p dir="auto">Here tested with "--safe"</p>
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="mfkinder@wk-boe001:~$ atom --safe
mfkinder@wk-boe001:~$ [14753:0213/170133:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[14783:0213/170133:INFO:renderer_main.cc(211)] Renderer process started
App load time: 303ms
[14753:0213/170135:INFO:CONSOLE(79)] &quot;Window load time: 1552ms&quot;, source: file:///usr/share/atom/resources/app/static/index.js (79)
The program 'atom' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 448 error_code 5 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)"><pre class="notranslate">mfkinder@wk-boe001:<span class="pl-k">~</span>$ atom --safe
mfkinder@wk-boe001:<span class="pl-k">~</span>$ [14753:0213/170133:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox<span class="pl-k">!</span> See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment <span class="pl-k">for</span> more information on developing with the sandbox on.
[14783:0213/170133:INFO:renderer_main.cc(211)] Renderer process started
App load time: 303ms
[14753:0213/170135:INFO:CONSOLE(79)] <span class="pl-s"><span class="pl-pds">"</span>Window load time: 1552ms<span class="pl-pds">"</span></span>, source: file:///usr/share/atom/resources/app/static/index.js (79)
The program <span class="pl-s"><span class="pl-pds">'</span>atom<span class="pl-pds">'</span></span> received an X Window System error.
This probably reflects a bug <span class="pl-k">in</span> the program.
The error was <span class="pl-s"><span class="pl-pds">'</span>BadAtom (invalid Atom parameter)<span class="pl-pds">'</span></span>.
  (Details: serial 448 error_code 5 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously<span class="pl-k">;</span>
   that is, you will receive the error a <span class="pl-k">while</span> after causing it.
   To debug your program, run it with the --sync <span class="pl-c1">command</span> line
   option to change this behavior. You can <span class="pl-k">then</span> get a meaningful
   backtrace from your debugger <span class="pl-k">if</span> you <span class="pl-c1">break</span> on the <span class="pl-en">gdk_x_error</span>() function.)</pre></div>
<p dir="auto">OS: Ubuntu 14.10 x64<br>
Plugins installed:<br>
mfkinder@wk-boe001:~$ apm list<br>
Built-in Atom packages (84)<br>
├── archive-view@0.47.0<br>
├── atom-dark-syntax@0.26.0<br>
├── atom-dark-ui@0.47.0<br>
├── atom-light-syntax@0.26.0<br>
├── atom-light-ui@0.41.0<br>
├── autocomplete@0.44.0<br>
├── autoflow@0.22.0<br>
├── autosave@0.20.0<br>
├── background-tips@0.22.0<br>
├── base16-tomorrow-dark-theme@0.25.0<br>
├── base16-tomorrow-light-theme@0.8.0<br>
├── bookmarks@0.35.0<br>
├── bracket-matcher@0.71.0<br>
├── command-palette@0.34.0<br>
├── deprecation-cop@0.36.0<br>
├── dev-live-reload@0.41.0<br>
├── encoding-selector@0.18.0<br>
├── exception-reporting@0.21.0<br>
├── find-and-replace@0.156.0<br>
├── fuzzy-finder@0.65.0<br>
├── git-diff@0.51.0<br>
├── go-to-line@0.30.0<br>
├── grammar-selector@0.45.0<br>
├── image-view@0.49.0<br>
├── incompatible-packages@0.22.0<br>
├── keybinding-resolver@0.27.0<br>
├── language-c@0.38.0<br>
├── language-clojure@0.12.0<br>
├── language-coffee-script@0.39.0<br>
├── language-csharp@0.5.0<br>
├── language-css@0.28.0<br>
├── language-gfm@0.63.0<br>
├── language-git@0.10.0<br>
├── language-go@0.21.0<br>
├── language-html@0.29.0<br>
├── language-hyperlink@0.12.2<br>
├── language-java@0.14.0<br>
├── language-javascript@0.56.0<br>
├── language-json@0.12.0<br>
├── language-less@0.24.0<br>
├── language-make@0.13.0<br>
├── language-mustache@0.11.0<br>
├── language-objective-c@0.15.0<br>
├── language-perl@0.10.0<br>
├── language-php@0.20.0<br>
├── language-property-list@0.8.0<br>
├── language-python@0.32.0<br>
├── language-ruby@0.48.0<br>
├── language-ruby-on-rails@0.18.0<br>
├── language-sass@0.34.0<br>
├── language-shellscript@0.12.0<br>
├── language-source@0.9.0<br>
├── language-sql@0.14.0<br>
├── language-text@0.6.0<br>
├── language-todo@0.16.0<br>
├── language-toml@0.15.0<br>
├── language-xml@0.28.0<br>
├── language-yaml@0.22.0<br>
├── link@0.30.0<br>
├── markdown-preview@0.134.0<br>
├── metrics@0.42.0<br>
├── notifications@0.27.0<br>
├── one-dark-syntax@0.3.0<br>
├── one-dark-ui@0.4.0<br>
├── one-light-syntax@0.3.0<br>
├── one-light-ui@0.3.0<br>
├── open-on-github@0.32.0<br>
├── package-generator@0.37.0<br>
├── release-notes@0.48.0<br>
├── settings-view@0.178.0<br>
├── snippets@0.72.0<br>
├── solarized-dark-syntax@0.32.0<br>
├── solarized-light-syntax@0.19.0<br>
├── spell-check@0.54.0<br>
├── status-bar@0.59.0<br>
├── styleguide@0.44.0<br>
├── symbols-view@0.82.0<br>
├── tabs@0.65.0<br>
├── timecop@0.29.0<br>
├── tree-view@0.154.0<br>
├── update-package-dependencies@0.8.0<br>
├── welcome@0.21.0<br>
├── whitespace@0.28.0<br>
└── wrap-guide@0.31.0</p>
<p dir="auto">/home/mfkinder/.atom/packages (11)<br>
├── atom-auto-uglify@0.4.0<br>
├── autocomplete-paths@1.0.2<br>
├── autocomplete-plus@2.1.6<br>
├── git-blame@0.4.0<br>
├── git-log@0.2.0<br>
├── git-tab-status@1.5.3<br>
├── language-mason@2.0.0<br>
├── linter@0.11.1<br>
├── linter-jshint@0.1.0<br>
├── seti-ui@0.6.3<br>
└── tabs-to-spaces@0.8.1</p>
<p dir="auto">Atom Version: 0.129.0<br>
Video of me triggering the bug: <a href="http://ara.sh/private/atom-crash.ogv" rel="nofollow">http://ara.sh/private/atom-crash.ogv</a><br>
Reproducible every time.</p>
<p dir="auto">Environment:<br>
Ubuntu 14.04 (all updates installed as of filing this issue)<br>
Unity desktop environment</p>
<p dir="auto">Repro steps:</p>
<ol dir="auto">
<li>Launch atom from the Terminal</li>
<li>Open a Firefox window (or use an existing one)</li>
<li>Drag the Firefox tab anywhere over the Atom window</li>
</ol>
<p dir="auto">Actual behavior:<br>
It crashes</p>
<p dir="auto">Expected behavior:<br>
Not crash :-)</p>
<p dir="auto">Additional Information:<br>
The terminal prints out the following after the crash:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[7950:0920/180947:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[7950:0920/180947:ERROR:browser_main_loop.cc(189)] GTK theme error: Unable to locate theme engine in module_path: &quot;pixmap&quot;,
ATTENTION: default value of option force_s3tc_enable overridden by environment.
App load time: 88ms
[7984:0920/180947:INFO:renderer_main.cc(227)] Renderer process started
[7950:0920/180948:INFO:CONSOLE(18)] &quot;Window load time: 778ms&quot;, source: /opt/atom/resources/app/src/window-bootstrap.js (18)
The program 'atom' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 1360 error_code 5 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)"><pre class="notranslate"><code class="notranslate">[7950:0920/180947:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[7950:0920/180947:ERROR:browser_main_loop.cc(189)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",
ATTENTION: default value of option force_s3tc_enable overridden by environment.
App load time: 88ms
[7984:0920/180947:INFO:renderer_main.cc(227)] Renderer process started
[7950:0920/180948:INFO:CONSOLE(18)] "Window load time: 778ms", source: /opt/atom/resources/app/src/window-bootstrap.js (18)
The program 'atom' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 1360 error_code 5 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
</code></pre></div>