Author Topic: core dump in 24.0.0.8  (Read 1696 times)

rowbearto

  • Senior Community Member
  • Posts: 1672
  • Hero Points: 119
core dump in 24.0.0.8
« on: October 09, 2019, 01:48:40 pm »
Read core-191008.txt on support for a download link.

I think I was dragging the scrollbar up in the bottom pane of the "Smart Open" when it happened.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1307
  • Hero Points: 121
Re: core dump in 24.0.0.8
« Reply #1 on: October 09, 2019, 02:14:05 pm »
Ok, I'll take a look at it once the download finishes.

Taeguk

  • Community Member
  • Posts: 17
  • Hero Points: 2
Re: core dump in 24.0.0.8
« Reply #2 on: October 11, 2019, 06:14:54 pm »
FYI,

I have seen SE v24.0.0.8 64-bit being unstable running on both Ubuntu 14.04 and Ubuntu 18.04. Have several instances where SE has locked up / frozen.

Taeguk

  • Community Member
  • Posts: 17
  • Hero Points: 2
Re: core dump in 24.0.0.8
« Reply #3 on: October 11, 2019, 07:23:39 pm »
Keep having SE v24 locking up / freezing. Seems to be when I am editing about 5 files and scrolling or transitioning between the buffers using the Doc Tabs at top of the editor window. Running 64-bit on Ubuntu 14.04, but have seen on Ubuntu 18.04 as well.

Looking at other posts with core dumps, it looks like SE v24 is unstable under Linux, will be going back to using SE v23 until SE v24 is fixed and more stable  :(

rowbearto

  • Senior Community Member
  • Posts: 1672
  • Hero Points: 119
Re: core dump in 24.0.0.8
« Reply #4 on: October 11, 2019, 08:22:23 pm »
Attached is stack trace running gdb on my system.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1307
  • Hero Points: 121
Re: core dump in 24.0.0.8
« Reply #5 on: October 11, 2019, 08:22:55 pm »
@Taeguk

Haven't seen any lockups so far.  When I'm not testing for other distributions, I run Ubuntu 18.04 as my work system.  But that doesn't necessarily mean anything since there are so many things that could be configured differently. 

If you're having to kill -9 to kill it, I'd recommend deleting any tag files for the projects you're working on, so you don't have to worry about an incompletely written tag file given you more problems.

If you can get it to lock up, it might help if you could attach to the vs_exe process, and get a stack trace using GDB.   If the vs_exe PID was 2321, then this command would do it:  "sudo gdb -p 2321"    Then type "bt" at the gdb prompt to get the stack trace.  That can help us narrow it down if it's locked up on a particular operation, rather than just waiting for events from the window system.

Are the tabs all for local files?  I can sometimes get a small delay switching to a remote file for a slow connection, but the only time I've seen it really get wedged is when a NFS mount got trashed, and the vs_exe process was in the un-interruptable state.  It seems unlikely, but you could check to see if the process state is "D" when you run "ps ax | grep vs_exe".  (none of that would be specific to v24 of course).

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1307
  • Hero Points: 121
Re: core dump in 24.0.0.8
« Reply #6 on: October 11, 2019, 08:37:38 pm »
Thanks rowbearto.  If you've got a running vs_exe, can you also send me the contents of /proc/VS_EXE_PID/maps?

rowbearto

  • Senior Community Member
  • Posts: 1672
  • Hero Points: 119
Re: core dump in 24.0.0.8
« Reply #7 on: October 11, 2019, 08:44:47 pm »
maps file is attached.

Taeguk

  • Community Member
  • Posts: 17
  • Hero Points: 2
Re: core dump in 24.0.0.8
« Reply #8 on: October 15, 2019, 07:42:15 pm »
SE v24.0.0.8 hang / freeze.

Prior to running again, I removed the following files per request from SE support:
in .slickedit/24.0.0/
   vslick.sta
   vrestore.sta
   filepos.slk  (did not have one)

Workspace:
   .vtg file
   .vpwhist file

I ran SE v24 and had 6 files open (6 file tabs), and was scrolling, and selecting between the windows. Then I did a References on a class member variable:
"Searching 'BreathTrigger.cpp' for references. Press any key to stop'

SE v24 became un-responsive, the window went dark and froze. I attached to the process with gdb and did a stack trace, make a snapshot of the screen, and grabbed a copy of the maps file. See attached.