Sublime Forum

Sublime 3126 hanging in futex code on CentOS 7 for open/new

#1

Sublime Text 3 has started hanging hanging for me sometime within the last 6 months. This is certainly happening on CentOS 7, and may have been happening in one of the Red Hat Enterprise Linux 6.7/6.8 builds.

Every time I try to open a file, create a new file, or save a file (maybe only save as), the editor stops responding to key and mouse events, although it repaints fine. Looking at the WCHAN field in ps, I see that we’re waiting on futex. A this point, only a kill will exit the program; it never becomes responsive again in that session, even after accidentally leaving it hanging for several days.

This happens whether or not I’ve imported my license, and with a brand-new installation in a local filesystem as well as over NFS. It happens even if I’ve started a clean environment with /usr/bin/env -i csh -f before running.

Sadly, I do have another CentOS 7 machine on a different network where Sublime is still working, so there is something I’m missing about the environment I’m running in. Here are some details from where it’s running:

% cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
% uname -a
Linux myhost.mydomain 3.10.0-327.36.3.el7.x86_64 #1 SMP Mon Oct 24 16:09:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

This is preventing me from using Sublime at all on this network. I’m having to make do with Atom. Any clues or suggestions for further troubleshooting are welcomed.

0 Likes

#2

Try a dev build and see if you have any better luck: https://www.sublimetext.com/3dev. We’ve fixed quite a number of issues in the dev builds, so we may have resolved what you are running into.

0 Likes

#3

Build 3142 behaves the same way as 3126 on my workstation (the original troublesome host): hang with wchan=_futex, this time in the license entry screen. However, since I was poking around again, I found that I can run both 3142 and 3126 on another server that recently came online (also CentOS 7.3.1611, FWIW). It so happens that 3142 started there without incident, indicating that the license was accepted before the hang.

So I have a local workaround and am unstuck. Thank you very much for the prompt response, and the prompting :slight_smile:

I’m happy to continue troubleshooting if it would help you.

0 Likes