Skip to content
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.

Sign up for GitHub

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

Jump to bottom

atom.io editor fails to start possibly due to issue with BIG-REQUESTS extension #301

Closed
vatral opened this issue Dec 13, 2016 · 0 comments
Closed

atom.io editor fails to start possibly due to issue with BIG-REQUESTS extension #301

vatral opened this issue Dec 13, 2016 · 0 comments
Labels
fix available

Comments

@vatral
Copy link
Contributor

vatral commented Dec 13, 2016

When starting it under NX, this happens:

$ atom -f
[4380:1213/145919:ERROR:browser_main_loop.cc(231)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
[4380:1213/145921:ERROR:browser_main_parts.cc(126)] X IO error received (X server probably went away)

The problem is described and discussed here: atom/atom#4360 and they suggest it's related to the BIG-REQUESTS extension. I have tried the x11trace -e workaround and it fixed it.

I have reproduced it on the 3.6.x branch.
@sunweaver sunweaver mentioned this issue Feb 5, 2017
Closed
@Hybrid512 Hybrid512 mentioned this issue Feb 21, 2018
Closed
uli42 added a commit to uli42/nx-libs that referenced this issue Oct 6, 2018
@uli42
nxagent: Fix an excessive request size limitation that broke big-requ…
da9d1a5 
…ests.

Fixes ArcticaProject#301, ArcticaProject#631

Backport from xorg-xserver:

  commit ca82d4bddf235c9b68d51d68636bab40eafb9889
  Author: Eric Anholt <eric@anholt.net>
  Date:   Fri Aug 31 13:00:23 2007 -0700

    Bug #7186: Fix an excessive request size limitation that broke big-requests.

    MAXBUFSIZE appears to be a leftover of some previous time.  Instead, just
    use maxBigRequestSize when bigreqs are available (limiting buffers to ~16MB).
    When bigreqs are not available, needed won't be larger than the maximum
    size of a non-bigreqs request (256kB).
@uli42 uli42 mentioned this issue Oct 6, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fix available
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vatral @uli42