Author Topic: 18.0.1.1 Crash  (Read 1445 times)

Tim Kemp

  • Senior Community Member
  • Posts: 531
  • Hero Points: 88
18.0.1.1 Crash
« on: August 15, 2013, 02:03:01 pm »
Since I updated I've had SlickEdit crash several times. Each time it was right after I clicked on the "Find" button in the "Find and Replace" dialog on the "Find in Files" tab. I had "Look in: <Workspace>" selected. The workspace contains a single project with 6796 files in it. The files are all on a local drive.

It seems like the time from when the "Find" button is clicked until the search starts is longer in version 18. Has anyone else noticed this?


SlickEdit 2013 (v18.0.1.1 32-bit)
Build Date: August 08, 2013
Emulation: CUA
OS: Windows 7
OS Version: 6.01.7601  Service Pack 1
Memory: 64% Load, 2047MB/3176MB Physical, 3226MB/6351MB Page File, 488MB/2047MB Virtual
Shell Info: C:\Windows\system32\cmd.exe /q
Screen Size: 1920 x 1080, 1920 x 1080

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1205
  • Hero Points: 116
Re: 18.0.1.1 Crash
« Reply #1 on: August 15, 2013, 02:10:53 pm »
Are there any wildcards in any of the projects?  And is it a SlickEdit project/workspace or another 3rdparty type?

Tim Kemp

  • Senior Community Member
  • Posts: 531
  • Hero Points: 88
Re: 18.0.1.1 Crash
« Reply #2 on: August 15, 2013, 02:26:35 pm »
I'm not sure what you mean about wildcards. The project name is 0652. It is a SlickEdit project and workspace.

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1205
  • Hero Points: 116
Re: 18.0.1.1 Crash
« Reply #3 on: August 15, 2013, 02:32:34 pm »
Were any files added to project using "Add as wildcard" (*.cpp) so that new files are picked up automatically?  And it is a single project in the workspace?

We haven't seen any issues like this so far.  We may need you to setup a support case so you can send in your workspace and project files (no source needed) to take a look see.


Tim Kemp

  • Senior Community Member
  • Posts: 531
  • Hero Points: 88
Re: 18.0.1.1 Crash
« Reply #4 on: August 15, 2013, 02:42:43 pm »
Yes, I created the project with a "*.*" wildcard. I didn't know that it would pick up new files. In fact, I've deleted all the files from projects and re-added files back in because there were new files that didn't get picked up automatically. Is this a new feature?

Yes, it's a single project in the workspace. It's very simple, just an "Other C/C++" type project. It contains all the files from a Perforce workspace. I don't build in that tree so all the files are under version control. I populated it by adding the whole tree.

I'd be glad to give you the workspace and project files. Just tell me how.

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1205
  • Hero Points: 116
Re: 18.0.1.1 Crash
« Reply #5 on: August 15, 2013, 03:08:53 pm »
Unless you specifically checked the "Add as wildcard" option when using Add Tree..., then all the files were added by name using a one-time search of files in the directory.  The wildcard option is more CPU/IO intensive, as it will do a directory search whenever the project file list is opened or refreshed.

On slickedit.com page there are links there for opening a support case.

Tim Kemp

  • Senior Community Member
  • Posts: 531
  • Hero Points: 88
Re: 18.0.1.1 Crash
« Reply #6 on: August 15, 2013, 03:26:10 pm »
I added the project and workspace files to support case CAS-64211-RJL9