Author Topic: Hang when doing find in file during build  (Read 10308 times)

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Hang when doing find in file during build
« on: January 10, 2017, 06:00:00 PM »
I'm occasionally able to hang the UI when doing a find in files while a build is running in the build window. It's not consistent and I don't have a good repro. Any known issues in this area? Any info I can get you when the hang happens?

SlickEdit Pro 2016 (v21.0.1.0 64-bit)

Serial number: VLX927636
Licensed number of users: Single user
License file: /opt/slickedit-pro2016/bin/slickedit.lic

Build Date: December 14, 2016
Emulation: CUA

OS: Linux
OS Version: Ubuntu 16.04.1 LTS
Kernel Level: 4.4.0-57-generic
Build Version: #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016
Processor Architecture: x86_64

X Server Vendor: The X.Org Foundation
Memory: 56% Load, 2008MB/3574MB Virtual
Shell Information: /opt/slickedit-pro2016/bin/secsh -i
Screen Size: 3840 x 2008

Project Type: (Other)
Language: No file open
Encoding: No file open

Installation Directory: /opt/slickedit-pro2016/
Configuration Directory: /home/mklein/.slickedit/21.0.1/
Migrated from: /home/mklein/.slickedit/21.0.0/

Hotfixes:
/home/mklein/.slickedit/21.0.1/hotfixes/hotfix_se2101_1_cumulative.zip (Revision: 1)



Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2896
  • Hero Points: 153
Re: Hang when doing find in file during build
« Reply #1 on: January 10, 2017, 06:25:30 PM »
Does it recover?

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: Hang when doing find in file during build
« Reply #2 on: January 10, 2017, 06:37:05 PM »
No, I have to force kill the process.

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: Hang when doing find in file during build
« Reply #3 on: January 11, 2017, 12:16:38 AM »
#0  0x00007fb0dd900f7b in __waitpid (pid=-1, stat_loc=0x7fff4e691dcc, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
#1  0x00000000017487e5 in cmProcess::unixWaitPid(int) ()
#2  0x00000000017489ee in cmProcess::getExitCode() ()
#3  0x000000000153ab1a in pipeEndProcess(cmProcess&) ()
#4  0x000000000077baa6 in vsPipeEndProcess ()
#5  0x000000000077c0ab in vsPipeProcess ()
#6  0x0000000000595073 in call_dllpc(int, int, namelist_t*) ()
#7  0x00000000007155ab in pmethod_op() ()
#8  0x00000000007155ab in pmethod_op() ()
#9  0x0000000000596b62 in run_proc(int) ()
#10 0x000000000074615b in call_key_common(filewindow_t*, int, int, unsigned int, unsigned int, bool, unsigned char) ()
#11 0x0000000000746377 in vs_call_keya(filewindow_t*, int, int) ()
#12 0x00000000005ed6e3 in vsCtlSlickCExecuteEvent ()
#13 0x00000000005f0141 in vsQTSlickCExecuteKeyEvent ()
#14 0x00000000005eb6c7 in vsCtlComboBox::keyPressEvent(QKeyEvent*) ()
#15 0x00000000007bee9c in vmyQComboBox::keyPressEvent(QKeyEvent*) ()
#16 0x00007fb0dbbd075c in QWidget::event(QEvent*) () from /opt/slickedit-pro2016/bin/libQtGui.so.4
#17 0x00007fb0dbb7dab4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /opt/slickedit-pro2016/bin/libQtGui.so.4
#18 0x00007fb0dbb82c4e in QApplication::notify(QObject*, QEvent*) () from /opt/slickedit-pro2016/bin/libQtGui.so.4
#19 0x00007fb0db61288c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /opt/slickedit-pro2016/bin/libQtCore.so.4
#20 0x00007fb0dbc1e8b9 in ?? () from /opt/slickedit-pro2016/bin/libQtGui.so.4
#21 0x00007fb0dbc1ecb5 in ?? () from /opt/slickedit-pro2016/bin/libQtGui.so.4
#22 0x00007fb0dbbfafd4 in QApplication::x11ProcessEvent(_XEvent*) () from /opt/slickedit-pro2016/bin/libQtGui.so.4
#23 0x00007fb0dbc22bb2 in ?? () from /opt/slickedit-pro2016/bin/libQtGui.so.4
#24 0x00007fb0d5d651a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007fb0d5d65400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007fb0d5d654ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007fb0db64091f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/slickedit-pro2016/bin/libQtCore.so.4
#28 0x00007fb0dbc2284e in ?? () from /opt/slickedit-pro2016/bin/libQtGui.so.4
#29 0x00007fb0db6112d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/slickedit-pro2016/bin/libQtCore.so.4
#30 0x00007fb0db611527 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/slickedit-pro2016/bin/libQtCore.so.4
#31 0x00007fb0db6167e7 in QCoreApplication::exec() () from /opt/slickedit-pro2016/bin/libQtCore.so.4
#32 0x00000000004eca4a in vmain(int, char**) ()
#33 0x0000000001530da9 in xmain ()
#34 0x000000000049e6e9 in main ()

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: Hang when doing find in file during build
« Reply #4 on: January 11, 2017, 01:44:29 AM »
There are no known hangs.

Try killing the external sgrep process next time this happens.

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: Hang when doing find in file during build
« Reply #5 on: March 03, 2017, 07:29:16 PM »
To circle back on this, the command that is hanging is:
/opt/slickedit-pro2016/bin/secsh -i

If I kill this command, the UI unlocks. Any other ideas?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: Hang when doing find in file during build
« Reply #6 on: March 03, 2017, 10:38:52 PM »
secsh is used to run processes in the build window. What process did you run in the build window?

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: Hang when doing find in file during build
« Reply #7 on: March 04, 2017, 03:35:11 AM »
A script that does a cmake C++ build. The build completes (I can tell via top), but the UI becomes locked up sometimes only when I open the find in files dialog. I never have any problems if I don't open the find in file dialog during a build. (And it doesn't always lock up).

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: Hang when doing find in file during build
« Reply #8 on: March 04, 2017, 01:40:52 PM »
Just displaying the find in files dialog (not even running it) it sometimes hangs?

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: Hang when doing find in file during build
« Reply #9 on: March 04, 2017, 04:56:55 PM »
I believe I have to actually start a find in files run, but I will confirm.

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: Hang when doing find in file during build
« Reply #10 on: July 06, 2017, 06:31:51 PM »
I'm still having trouble with this.

I've tried switching the shell from secsh to dash as well as bash. I've seen the hang with dash but not yet with bash. When the UI is hung, beyond killing the shell (which FYI no longer seems to fix things. It just gets into a weird state where the find window is still there but blank, but I can at least exit the process via closing in the command bar).

Is there anything I can do to help figure out why things are getting hung up?

I do seem to have to initiate a search for the hang to happen.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2896
  • Hero Points: 153
Re: Hang when doing find in file during build
« Reply #11 on: July 06, 2017, 07:18:38 PM »
Do you have "Foreground search" turned on?

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: Hang when doing find in file during build
« Reply #12 on: July 06, 2017, 08:01:55 PM »
No, the checkbox is disabled and I have never enabled it AFAIK (I don't know what it does).

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: Hang when doing find in file during build
« Reply #13 on: July 17, 2017, 07:59:25 PM »
Bump. Anything I can do to help debug this? It's super annoying.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: Hang when doing find in file during build
« Reply #14 on: July 17, 2017, 08:59:49 PM »
Wish we could reproduce this. If you dump the slickedit process stack, does it always look the same? (In waitpid).