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

Crash on Ubuntu when dragging a Firefox window over Atom #3593

Closed
arashpayan opened this Issue Sep 21, 2014 · 42 comments

Comments

Projects
None yet
@arashpayan

arashpayan commented Sep 21, 2014

Atom Version: 0.129.0
Video of me triggering the bug: http://ara.sh/private/atom-crash.ogv
Reproducible every time.

Environment:
Ubuntu 14.04 (all updates installed as of filing this issue)
Unity desktop environment

Repro steps:

  1. Launch atom from the Terminal
  2. Open a Firefox window (or use an existing one)
  3. Drag the Firefox tab anywhere over the Atom window

Actual behavior:
It crashes

Expected behavior:
Not crash :-)

Additional Information:
The terminal prints out the following after the crash:

[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.)
@lee-dohm

This comment has been minimized.

Show comment
Hide comment
@lee-dohm

lee-dohm Sep 21, 2014

Member

Just for information, on Atom v0.130.0-5cc62b2 and OS X v10.9.5, this does not reproduce.

Member

lee-dohm commented Sep 21, 2014

Just for information, on Atom v0.130.0-5cc62b2 and OS X v10.9.5, this does not reproduce.

@batjko

This comment has been minimized.

Show comment
Hide comment
@batjko

batjko Sep 21, 2014

Contributor

Can't reproduce this on v130 on Elementary OS either, I'm afraid.

Contributor

batjko commented Sep 21, 2014

Can't reproduce this on v130 on Elementary OS either, I'm afraid.

@arashpayan

This comment has been minimized.

Show comment
Hide comment
@arashpayan

arashpayan Sep 21, 2014

I suspect it's related to running Ubuntu's Unity desktop environment.

arashpayan commented Sep 21, 2014

I suspect it's related to running Ubuntu's Unity desktop environment.

@arashpayan

This comment has been minimized.

Show comment
Hide comment
@arashpayan

arashpayan Sep 24, 2014

Just tested against v0.130 on Ubuntu and it still occurs.

arashpayan commented Sep 24, 2014

Just tested against v0.130 on Ubuntu and it still occurs.

@necavit

This comment has been minimized.

Show comment
Hide comment
@necavit

necavit Oct 4, 2014

Same behaviour here. Also reproducible every time.

Environment:

  • Ubuntu 12.04
  • Unity desktop environment

Reproducing steps (same as @arashpayan reported):

  1. Launch atom from the Terminal
  2. Open a Firefox window (or use an existing one)
  3. Drag the Firefox tab anywhere over the Atom window

Terminal output:

[3440:1004/111601: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.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
App load time: 92ms
[3472:1004/111602:INFO:renderer_main.cc(227)] Renderer process started
[3440:1004/111603:INFO:CONSOLE(11)] "activate linter-clang", source: /home/username/.atom/packages/linter-clang/lib/init.coffee (11)
[3440:1004/111603:INFO:CONSOLE(7)] "activate linter-javac", source: /home/username/.atom/packages/linter-javac/lib/init.coffee (7)
[3440:1004/111603:INFO:CONSOLE(4)] "Linter-Pylint: package loaded, ready to get initialized by AtomLinter.", source: /home/username/.atom/packages/linter-pylint/lib/init.coffee (4)
[3440:1004/111603:INFO:CONSOLE(7)] "activate linter-shellcheck", source: /home/username/.atom/packages/linter-shellcheck/lib/init.coffee (7)
[3440:1004/111603:INFO:CONSOLE(7)] "activate linter-xmllint", source: /home/username/.atom/packages/linter-xmllint/lib/init.coffee (7)
[3440:1004/111605:INFO:CONSOLE(18)] "Window load time: 3359ms", 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 3707 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.)

necavit commented Oct 4, 2014

Same behaviour here. Also reproducible every time.

Environment:

  • Ubuntu 12.04
  • Unity desktop environment

Reproducing steps (same as @arashpayan reported):

  1. Launch atom from the Terminal
  2. Open a Firefox window (or use an existing one)
  3. Drag the Firefox tab anywhere over the Atom window

Terminal output:

[3440:1004/111601: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.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
App load time: 92ms
[3472:1004/111602:INFO:renderer_main.cc(227)] Renderer process started
[3440:1004/111603:INFO:CONSOLE(11)] "activate linter-clang", source: /home/username/.atom/packages/linter-clang/lib/init.coffee (11)
[3440:1004/111603:INFO:CONSOLE(7)] "activate linter-javac", source: /home/username/.atom/packages/linter-javac/lib/init.coffee (7)
[3440:1004/111603:INFO:CONSOLE(4)] "Linter-Pylint: package loaded, ready to get initialized by AtomLinter.", source: /home/username/.atom/packages/linter-pylint/lib/init.coffee (4)
[3440:1004/111603:INFO:CONSOLE(7)] "activate linter-shellcheck", source: /home/username/.atom/packages/linter-shellcheck/lib/init.coffee (7)
[3440:1004/111603:INFO:CONSOLE(7)] "activate linter-xmllint", source: /home/username/.atom/packages/linter-xmllint/lib/init.coffee (7)
[3440:1004/111605:INFO:CONSOLE(18)] "Window load time: 3359ms", 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 3707 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.)
@zcbenz

This comment has been minimized.

Show comment
Hide comment
@zcbenz

zcbenz Oct 5, 2014

Member

Full stack trace:

#0  0x00007fffeff650e0 in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#1  0x00007fffeff621d1 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#2  0x00007fffeff63157 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#3  0x00007fffeff48da6 in XGetWindowProperty ()
   from /usr/lib/x86_64-linux-gnu/libX11.so.6
#4  0x00007ffff4b09a3b in ui::GetRawBytesOfProperty(unsigned long, unsigned long, scoped_refptr<base::RefCountedMemory>*, unsigned long*, unsigned long*, unsigned long*) () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#5  0x0000000000b9b3ab in views::DesktopDragDropClientAuraX11::X11DragContext::OnSelectionNotify (this=0x1ef103c33000, event=...)
    at ../../ui/views/widget/desktop_aura/desktop_drag_drop_client_aurax11.cc:271
#6  0x0000000000b9b455 in views::DesktopDragDropClientAuraX11::OnSelectionNotify (this=0x1ef103b0c340, xselection=...)
    at ../../ui/views/widget/desktop_aura/desktop_drag_drop_client_aurax11.cc:566
#7  0x0000000000b4fd3f in views::DesktopWindowTreeHostX11::DispatchEvent (
    this=0x1ef103b0c080, event=@0x7fffffffd828: 0x7fffffffd900)
    at ../../ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc:1802
#8  0x00007ffff4b1a287 in ui::PlatformEventSource::DispatchEvent(_XEvent*) ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#9  0x00007ffff4b33b0c in ui::X11EventSource::DispatchEvent(_XEvent*) ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
---Type <return> to continue, or q <return> to quit---
#10 0x00007ffff4b33a5e in ui::X11EventSource::DispatchXEvents() ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#11 0x00007ffff4b33bbc in ?? ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#12 0x00007ffff14acd13 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff14ad060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff14ad124 in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff3ddf5df in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#16 0x00007ffff3e46438 in base::RunLoop::Run() ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#17 0x00007ffff3ea419c in content::BrowserMainLoop::MainMessageLoopRun() ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#18 0x00007ffff3ea4210 in content::BrowserMainLoop::RunMainMessageLoopParts()
    () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#19 0x00007ffff3ea696d in ?? ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#20 0x00007ffff3ea0349 in content::BrowserMain(content::MainFunctionParams const&) () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#21 0x00007ffff3dd39ac in ?? ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
---Type <return> to continue, or q <return> to quit---
#22 0x00007ffff3dd1f01 in content::ContentMain(content::ContentMainParams const&) () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#23 0x000000000066de90 in main (argc=2, argv=0x7fffffffde18)
    at ../../atom/app/atom_main.cc:123

Somehow dragging the tab of firebox triggered a SelectionNotify event, which should only happen on clipboard copy/paste, and I'm not sure why Chromium is not affected.

Member

zcbenz commented Oct 5, 2014

Full stack trace:

#0  0x00007fffeff650e0 in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#1  0x00007fffeff621d1 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#2  0x00007fffeff63157 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#3  0x00007fffeff48da6 in XGetWindowProperty ()
   from /usr/lib/x86_64-linux-gnu/libX11.so.6
#4  0x00007ffff4b09a3b in ui::GetRawBytesOfProperty(unsigned long, unsigned long, scoped_refptr<base::RefCountedMemory>*, unsigned long*, unsigned long*, unsigned long*) () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#5  0x0000000000b9b3ab in views::DesktopDragDropClientAuraX11::X11DragContext::OnSelectionNotify (this=0x1ef103c33000, event=...)
    at ../../ui/views/widget/desktop_aura/desktop_drag_drop_client_aurax11.cc:271
#6  0x0000000000b9b455 in views::DesktopDragDropClientAuraX11::OnSelectionNotify (this=0x1ef103b0c340, xselection=...)
    at ../../ui/views/widget/desktop_aura/desktop_drag_drop_client_aurax11.cc:566
#7  0x0000000000b4fd3f in views::DesktopWindowTreeHostX11::DispatchEvent (
    this=0x1ef103b0c080, event=@0x7fffffffd828: 0x7fffffffd900)
    at ../../ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc:1802
#8  0x00007ffff4b1a287 in ui::PlatformEventSource::DispatchEvent(_XEvent*) ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#9  0x00007ffff4b33b0c in ui::X11EventSource::DispatchEvent(_XEvent*) ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
---Type <return> to continue, or q <return> to quit---
#10 0x00007ffff4b33a5e in ui::X11EventSource::DispatchXEvents() ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#11 0x00007ffff4b33bbc in ?? ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#12 0x00007ffff14acd13 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff14ad060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff14ad124 in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff3ddf5df in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#16 0x00007ffff3e46438 in base::RunLoop::Run() ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#17 0x00007ffff3ea419c in content::BrowserMainLoop::MainMessageLoopRun() ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#18 0x00007ffff3ea4210 in content::BrowserMainLoop::RunMainMessageLoopParts()
    () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#19 0x00007ffff3ea696d in ?? ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#20 0x00007ffff3ea0349 in content::BrowserMain(content::MainFunctionParams const&) () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#21 0x00007ffff3dd39ac in ?? ()
   from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
---Type <return> to continue, or q <return> to quit---
#22 0x00007ffff3dd1f01 in content::ContentMain(content::ContentMainParams const&) () from /home/zcbenz/codes/atom-shell/out/Debug/libchromiumcontent.so
#23 0x000000000066de90 in main (argc=2, argv=0x7fffffffde18)
    at ../../atom/app/atom_main.cc:123

Somehow dragging the tab of firebox triggered a SelectionNotify event, which should only happen on clipboard copy/paste, and I'm not sure why Chromium is not affected.

@ingalls

This comment has been minimized.

Show comment
Hide comment
@ingalls

ingalls Dec 18, 2014

I'm currently running GNOME Shell 3.10.4 on Ubuntu without unity installed and can confirm that this error is deeper than just unity.

ingalls commented Dec 18, 2014

I'm currently running GNOME Shell 3.10.4 on Ubuntu without unity installed and can confirm that this error is deeper than just unity.

@oalexandersson

This comment has been minimized.

Show comment
Hide comment
@oalexandersson

oalexandersson Jan 8, 2015

Atom version 0.158.0
OS: Ubuntu 14.10
Desktop: XFCE 4.10

100% reproducible. Definitely not Unity related. It's really annoying; when you move a tab out to create a new browser window with that tab, you have to be super careful to not move it over the atom window.

oalexandersson commented Jan 8, 2015

Atom version 0.158.0
OS: Ubuntu 14.10
Desktop: XFCE 4.10

100% reproducible. Definitely not Unity related. It's really annoying; when you move a tab out to create a new browser window with that tab, you have to be super careful to not move it over the atom window.

@cmtonkinson

This comment has been minimized.

Show comment
Hide comment
@cmtonkinson

cmtonkinson Feb 8, 2015

Atom: 0.1770
OS: Arch Linux
Desktop: GNOME Shell 3.14.3

Same thing, every time. Note that reproduction has nothing to do with how Atom is started (e.g. by the terminal) it just affects whether you see this error.

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 764 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.)

cmtonkinson commented Feb 8, 2015

Atom: 0.1770
OS: Arch Linux
Desktop: GNOME Shell 3.14.3

Same thing, every time. Note that reproduction has nothing to do with how Atom is started (e.g. by the terminal) it just affects whether you see this error.

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 764 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.)
@bglass

This comment has been minimized.

Show comment
Hide comment
@bglass

bglass Feb 25, 2015

Atom version 0.181.0
OS: Ubuntu 14.10
Desktop: KDE 4.14.1

Same behaviour with KDE.
(crash when dragging Firefox Tab over Atom)

bglass commented Feb 25, 2015

Atom version 0.181.0
OS: Ubuntu 14.10
Desktop: KDE 4.14.1

Same behaviour with KDE.
(crash when dragging Firefox Tab over Atom)

@slang800

This comment has been minimized.

Show comment
Hide comment
@slang800

slang800 Mar 23, 2015

Just found this on Ubuntu-GNOME 14.10 with Atom v0.187

slang800 commented Mar 23, 2015

Just found this on Ubuntu-GNOME 14.10 with Atom v0.187

@50Wliu 50Wliu added the crash label Mar 24, 2015

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Apr 3, 2015

Same for me, Ubuntu 14.10 with Atom v0.187, every time.

ghost commented Apr 3, 2015

Same for me, Ubuntu 14.10 with Atom v0.187, every time.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Apr 3, 2015

Moreover, it also breaks Firefox as well, if you try to drag just one tab from Firefox over Atom and then place it back, you'll see, that it will disappear also, and break tabs order.

ghost commented Apr 3, 2015

Moreover, it also breaks Firefox as well, if you try to drag just one tab from Firefox over Atom and then place it back, you'll see, that it will disappear also, and break tabs order.

@mattcollier

This comment has been minimized.

Show comment
Hide comment
@mattcollier

mattcollier Apr 8, 2015

Debian Jessie x64 with iceweasel, Atom 0.189.0. Atom just disappears if iceweasel tab is dragged over atom window. This is in the console:

The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 618 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.)

mattcollier commented Apr 8, 2015

Debian Jessie x64 with iceweasel, Atom 0.189.0. Atom just disappears if iceweasel tab is dragged over atom window. This is in the console:

The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 618 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.)
@johnfraney

This comment has been minimized.

Show comment
Hide comment
@johnfraney

johnfraney Apr 8, 2015

I've found that the crash happens when dragging even just an image. (Atom v0.190.0, Arch x64.)

johnfraney commented Apr 8, 2015

I've found that the crash happens when dragging even just an image. (Atom v0.190.0, Arch x64.)

@johnfraney

This comment has been minimized.

Show comment
Hide comment
@johnfraney

johnfraney Apr 23, 2015

I can confirm that this issue is still present in 0.194.0 (Arch x64, Firefox Developer Edition 39.0a2).

johnfraney commented Apr 23, 2015

I can confirm that this issue is still present in 0.194.0 (Arch x64, Firefox Developer Edition 39.0a2).

@espace3d

This comment has been minimized.

Show comment
Hide comment
@espace3d

espace3d Apr 26, 2015

what is the solution to prevent that ?

espace3d commented Apr 26, 2015

what is the solution to prevent that ?

@JakobBerg

This comment has been minimized.

Show comment
Hide comment
@JakobBerg

JakobBerg Apr 29, 2015

getting same crash the moment I hover a window from firefox over Atom User Interface

running atom

:~$ atom --safe
:~$ [8179:0429/182252:ERROR:browser_main_loop.cc(170)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
App load time: 139ms
[8211:0429/182252:INFO:renderer_main.cc(212)] Renderer process started
[8179:0429/182253:INFO:CONSOLE(59)] "Window load time: 798ms", source: file:///opt/atom/resources/app.asar/static/index.js (59)
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 586 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.)

Command History

     -0:19.2 ready (#document)
     -0:19.0 pane:item-added (atom-pane.pane.active)
     -0:19.0 pane-container:active-pane-item-changed (atom-pane-container.panes)
     -0:18.9 editor:attached (atom-text-editor.editor.is-focused)
     -0:18.9 pane:active-item-changed (atom-pane.pane.active)
     -0:18.9 uri-opened (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:01.8 command-palette:toggle (atom-text-editor.editor.is-focused)
     -0:00.0 core:confirm (atom-text-editor.editor.mini)
     -0:00.0 bug-report:open (atom-text-editor.editor.is-focused)

Versions

  • Atom: 0.194.0
  • Atom-Shell: 0.22.3
  • OS: linux 3.16.0-33-generic
    • Ubuntu 14.04.2 LTS 64 bit (standard setup with unity)
  • Misc
    • apm 0.161.0
    • npm 2.5.1
    • node 0.10.35
    • python 2.7.6
    • git 1.9.1
    • firefox 37.0.2

JakobBerg commented Apr 29, 2015

getting same crash the moment I hover a window from firefox over Atom User Interface

running atom

:~$ atom --safe
:~$ [8179:0429/182252:ERROR:browser_main_loop.cc(170)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
App load time: 139ms
[8211:0429/182252:INFO:renderer_main.cc(212)] Renderer process started
[8179:0429/182253:INFO:CONSOLE(59)] "Window load time: 798ms", source: file:///opt/atom/resources/app.asar/static/index.js (59)
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 586 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.)

Command History

     -0:19.2 ready (#document)
     -0:19.0 pane:item-added (atom-pane.pane.active)
     -0:19.0 pane-container:active-pane-item-changed (atom-pane-container.panes)
     -0:18.9 editor:attached (atom-text-editor.editor.is-focused)
     -0:18.9 pane:active-item-changed (atom-pane.pane.active)
     -0:18.9 uri-opened (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:01.8 command-palette:toggle (atom-text-editor.editor.is-focused)
     -0:00.0 core:confirm (atom-text-editor.editor.mini)
     -0:00.0 bug-report:open (atom-text-editor.editor.is-focused)

Versions

  • Atom: 0.194.0
  • Atom-Shell: 0.22.3
  • OS: linux 3.16.0-33-generic
    • Ubuntu 14.04.2 LTS 64 bit (standard setup with unity)
  • Misc
    • apm 0.161.0
    • npm 2.5.1
    • node 0.10.35
    • python 2.7.6
    • git 1.9.1
    • firefox 37.0.2

@croaker000

This comment has been minimized.

Show comment
Hide comment
@croaker000

croaker000 Jul 30, 2015

In my experience (Ubuntu), dragging any drop candidate from anything to anywhere that passes over an open Atom window will cause the drag/drop to fail with varying fallout depending on how that failure is handled by the parent program. I've resorted to either minimising Atom or moving the source and target windows so that the drag does not pass over an Atom window.

croaker000 commented Jul 30, 2015

In my experience (Ubuntu), dragging any drop candidate from anything to anywhere that passes over an open Atom window will cause the drag/drop to fail with varying fallout depending on how that failure is handled by the parent program. I've resorted to either minimising Atom or moving the source and target windows so that the drag does not pass over an Atom window.

@mnquintana

This comment has been minimized.

Show comment
Hide comment
@mnquintana

mnquintana Jul 30, 2015

Member

@zcbenz Is this still an issue with latest Electron?

Member

mnquintana commented Jul 30, 2015

@zcbenz Is this still an issue with latest Electron?

@muchweb

This comment has been minimized.

Show comment
Hide comment
@muchweb

muchweb Jul 30, 2015

In my experience (Ubuntu), dragging any drop candidate from anything to anywhere that passes over an open Atom window will cause the drag/drop to fail

I am only experiencing crashes with Firefox/PaleMoon/Thunderbird. Any other drag&drop, including text, files and tabs from other programs work fine.

muchweb commented Jul 30, 2015

In my experience (Ubuntu), dragging any drop candidate from anything to anywhere that passes over an open Atom window will cause the drag/drop to fail

I am only experiencing crashes with Firefox/PaleMoon/Thunderbird. Any other drag&drop, including text, files and tabs from other programs work fine.

@croaker000

This comment has been minimized.

Show comment
Hide comment
@croaker000

croaker000 Jul 30, 2015

I am only experiencing crashes with Firefox/PaleMoon/Thunderbird.

Archive Manager (file-roller)? Nautilus? They're on my list...

croaker000 commented Jul 30, 2015

I am only experiencing crashes with Firefox/PaleMoon/Thunderbird.

Archive Manager (file-roller)? Nautilus? They're on my list...

@muchweb

This comment has been minimized.

Show comment
Hide comment
@muchweb

muchweb Jul 30, 2015

Archive Manager (file-roller)? Nautilus? They're on my list...

@croaker000, you are right, Archive Manager (file-roller) caused crash too. Although Thunar file manager worked fine.

muchweb commented Jul 30, 2015

Archive Manager (file-roller)? Nautilus? They're on my list...

@croaker000, you are right, Archive Manager (file-roller) caused crash too. Although Thunar file manager worked fine.

@hookenz

This comment has been minimized.

Show comment
Hide comment
@hookenz

hookenz Aug 5, 2015

I have the same issue on 14.04

hookenz commented Aug 5, 2015

I have the same issue on 14.04

@csouth

This comment has been minimized.

Show comment
Hide comment
@csouth

csouth Aug 7, 2015

@mnquintana I can confirm that the issue still exists with 0.30.2 of Electron. I can reproduce by just running Electron by itself and dragging a tab over it.

christian@laptop:~$ electron
[14195:0807/101135:ERROR:browser_main_loop.cc(173)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[14224:0807/101135:INFO:renderer_main.cc(200)] Renderer process started
[14213:0807/101135:ERROR:gles2_cmd_decoder.cc(11539)] [GroupMarkerNotSet(crbug.com/242999)!:D06658A9FA1A0000]GL ERROR :GL_INVALID_OPERATION : glTexStorage2DEXT: <- error from previous GL command

Then I drag a tab and the error occurs.

The program 'electron' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 390 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.)

csouth commented Aug 7, 2015

@mnquintana I can confirm that the issue still exists with 0.30.2 of Electron. I can reproduce by just running Electron by itself and dragging a tab over it.

christian@laptop:~$ electron
[14195:0807/101135:ERROR:browser_main_loop.cc(173)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[14224:0807/101135:INFO:renderer_main.cc(200)] Renderer process started
[14213:0807/101135:ERROR:gles2_cmd_decoder.cc(11539)] [GroupMarkerNotSet(crbug.com/242999)!:D06658A9FA1A0000]GL ERROR :GL_INVALID_OPERATION : glTexStorage2DEXT: <- error from previous GL command

Then I drag a tab and the error occurs.

The program 'electron' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 390 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.)

@mnquintana mnquintana added the blocked label Aug 7, 2015

@mnquintana

This comment has been minimized.

Show comment
Hide comment
@mnquintana

mnquintana Aug 7, 2015

Member

@csouth Thanks for the update! Though that's a bummer 😕 - marking this as blocked on electron/electron#2204 then.

Member

mnquintana commented Aug 7, 2015

@csouth Thanks for the update! Though that's a bummer 😕 - marking this as blocked on electron/electron#2204 then.

@Wulf

This comment has been minimized.

Show comment
Hide comment
@Wulf

Wulf Oct 3, 2015

I'm having the same problem: Arch + GNOME.

Hovering a Firefox tab over Atom makes it crash! (instantly)

Wulf commented Oct 3, 2015

I'm having the same problem: Arch + GNOME.

Hovering a Firefox tab over Atom makes it crash! (instantly)

@forivall

This comment has been minimized.

Show comment
Hide comment
@forivall

forivall Oct 3, 2015

Same here; also, dragging files from Dolphin (KDE SC file manager) crashes atom. It's likely the same issue. Manjaro (Arch based) + KDE.

forivall commented Oct 3, 2015

Same here; also, dragging files from Dolphin (KDE SC file manager) crashes atom. It's likely the same issue. Manjaro (Arch based) + KDE.

@martpie

This comment has been minimized.

Show comment
Hide comment
@martpie

martpie commented Oct 4, 2015

@50Wliu

This comment has been minimized.

Show comment
Hide comment
@50Wliu

50Wliu Oct 4, 2015

Member

Fixed in electron-archive/brightray#149 so

Once @zcbenz releases a new version of Electron I'll remove the blocked tag. Hopefully we can get it in #8779 as well 😄.

Member

50Wliu commented Oct 4, 2015

Fixed in electron-archive/brightray#149 so

Once @zcbenz releases a new version of Electron I'll remove the blocked tag. Hopefully we can get it in #8779 as well 😄.

@50Wliu 50Wliu added the electron label Oct 4, 2015

@crsaracco

This comment has been minimized.

Show comment
Hide comment
@crsaracco

crsaracco Oct 5, 2015

Same problem on Arch + Cinnamon.

crsaracco commented Oct 5, 2015

Same problem on Arch + Cinnamon.

@50Wliu 50Wliu removed the blocked label Oct 5, 2015

@zcbenz zcbenz referenced this issue Oct 5, 2015

Merged

Update to Electron v0.33.x #8779

21 of 21 tasks complete
@50Wliu

This comment has been minimized.

Show comment
Hide comment
@50Wliu

50Wliu Oct 5, 2015

Member

This will be fixed when #8779 is merged.

Member

50Wliu commented Oct 5, 2015

This will be fixed when #8779 is merged.

@shantee

This comment has been minimized.

Show comment
Hide comment
@shantee

shantee Oct 13, 2015

Same bug on Linux Mint 17.2 + Cinnamon

shantee commented Oct 13, 2015

Same bug on Linux Mint 17.2 + Cinnamon

@cmtonkinson

This comment has been minimized.

Show comment
Hide comment
@cmtonkinson

cmtonkinson Oct 30, 2015

Just updated this morning and I still experience this error. Firefox 41.0.2, Atom 1.1.0, Node 4.2.1, Linux 4.2.5, NPM 3.3.9.

En/Disabling hardware acceleration does not make a difference.

[6042:1030/081415:ERROR:browser_main_loop.cc(173)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
App load time: 191ms
[6100:1030/081416:ERROR:sandbox_linux.cc(340)] InitializeSandbox() called with multiple threads in process gpu-process
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6119:1030/081416:INFO:renderer_main.cc(200)] Renderer process started
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6130:1030/081416:INFO:renderer_main.cc(200)] Renderer process started
[6042:1030/081417:INFO:CONSOLE(46)] "Window load time: 1022ms", source: file:///usr/share/atom/resources/app.asar/static/index.js (46)
[6042:1030/081417:INFO:CONSOLE(46)] "Window load time: 942ms", source: file:///usr/share/atom/resources/app.asar/static/index.js (46)
[6042:1030/081417:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081417:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081417:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081417:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6100:1030/081418:ERROR:gles2_cmd_decoder.cc(11539)] [GroupMarkerNotSet(crbug.com/242999)!:D03810D4C5280000]GL ERROR :GL_INVALID_OPERATION : glTexStorage2DEXT: <- error from previous GL command
[6100:1030/081418:ERROR:gles2_cmd_decoder.cc(11539)] [GroupMarkerNotSet(crbug.com/242999)!:D0047CD4C5280000]GL ERROR :GL_INVALID_OPERATION : glTexStorage2DEXT: <- error from previous GL command
[6042:1030/081418:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081418:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081418:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081418:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
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 928 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.)

cmtonkinson commented Oct 30, 2015

Just updated this morning and I still experience this error. Firefox 41.0.2, Atom 1.1.0, Node 4.2.1, Linux 4.2.5, NPM 3.3.9.

En/Disabling hardware acceleration does not make a difference.

[6042:1030/081415:ERROR:browser_main_loop.cc(173)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
App load time: 191ms
[6100:1030/081416:ERROR:sandbox_linux.cc(340)] InitializeSandbox() called with multiple threads in process gpu-process
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6119:1030/081416:INFO:renderer_main.cc(200)] Renderer process started
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081416:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6130:1030/081416:INFO:renderer_main.cc(200)] Renderer process started
[6042:1030/081417:INFO:CONSOLE(46)] "Window load time: 1022ms", source: file:///usr/share/atom/resources/app.asar/static/index.js (46)
[6042:1030/081417:INFO:CONSOLE(46)] "Window load time: 942ms", source: file:///usr/share/atom/resources/app.asar/static/index.js (46)
[6042:1030/081417:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081417:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081417:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081417:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6100:1030/081418:ERROR:gles2_cmd_decoder.cc(11539)] [GroupMarkerNotSet(crbug.com/242999)!:D03810D4C5280000]GL ERROR :GL_INVALID_OPERATION : glTexStorage2DEXT: <- error from previous GL command
[6100:1030/081418:ERROR:gles2_cmd_decoder.cc(11539)] [GroupMarkerNotSet(crbug.com/242999)!:D0047CD4C5280000]GL ERROR :GL_INVALID_OPERATION : glTexStorage2DEXT: <- error from previous GL command
[6042:1030/081418:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081418:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081418:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[6042:1030/081418:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
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 928 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.)
@mnquintana

This comment has been minimized.

Show comment
Hide comment
@mnquintana

mnquintana Oct 30, 2015

Member

@cmtonkinson I think this was fixed for Atom 1.2.0, not 1.1.0 - feel free to try out the 1.2.0 beta if you want to test this fix out for yourself!

Member

mnquintana commented Oct 30, 2015

@cmtonkinson I think this was fixed for Atom 1.2.0, not 1.1.0 - feel free to try out the 1.2.0 beta if you want to test this fix out for yourself!

@cmtonkinson

This comment has been minimized.

Show comment
Hide comment
@cmtonkinson

cmtonkinson Oct 30, 2015

Not to be dense, but was the release post incorrect then?

Under the heading Upgrade to Electron 0.34.x near the bottom, it reads:

This brings Atom up to the latest version of Electron and fixes a couple of pretty bad, long-standing bugs.

Note that "pretty" links to this issue (#3593).

cmtonkinson commented Oct 30, 2015

Not to be dense, but was the release post incorrect then?

Under the heading Upgrade to Electron 0.34.x near the bottom, it reads:

This brings Atom up to the latest version of Electron and fixes a couple of pretty bad, long-standing bugs.

Note that "pretty" links to this issue (#3593).

@xgdgsc

This comment has been minimized.

Show comment
Hide comment
@xgdgsc

xgdgsc Oct 30, 2015

@cmtonkinson That' s in the "Available now in Atom 1.2.0-beta" section

xgdgsc commented Oct 30, 2015

@cmtonkinson That' s in the "Available now in Atom 1.2.0-beta" section

@cmtonkinson

This comment has been minimized.

Show comment
Hide comment
@cmtonkinson

cmtonkinson Oct 30, 2015

D'OH!

Obviously that's my bad. Apologies for the noise.

cmtonkinson commented Oct 30, 2015

D'OH!

Obviously that's my bad. Apologies for the noise.

@carbsrule

This comment has been minimized.

Show comment
Hide comment
@carbsrule

carbsrule Dec 18, 2015

Was experiencing this all the time dragging Iceweasel tabs (on Debian 8.1 with Cinnamon).
Upgraded from v1.1.0 to 1.3.2 and the problem seems to have gone away. Huzzah!

carbsrule commented Dec 18, 2015

Was experiencing this all the time dragging Iceweasel tabs (on Debian 8.1 with Cinnamon).
Upgraded from v1.1.0 to 1.3.2 and the problem seems to have gone away. Huzzah!

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