B6 Windows x64: Crash closing one particular file

[jnairb]

I was having a problem with SlickEdit 19 beta5 & 6 crashing when I tried to close a project (workspace-reset) and tracked the issue down to it crashing when I try to close (quit command) one particular file that I had open. Here's the crash info from Windows Application Event Log:

Faulting application name: vs.exe, version: 19.0.0.9, time stamp: 0x5429887a
Faulting module name: vsapi.dll, version: 19.0.0.9, time stamp: 0x54298781
Exception code: 0xc0000005
Fault offset: 0x00000000000de510
Faulting process id: 0x1038
Faulting application start time: 0x01cfdd95487ab8a9
Faulting application path: c:\Program Files\SlickEdit\beta\win\vs.exe
Faulting module path: c:\Program Files\SlickEdit\beta\win\vsapi.dll
Report Id: 5a54e017-4989-11e4-bca9-0002721959c4

Here's my SE version info:

SlickEdit 2014 (v19.0.0.9 64-bit)

Serial number: FE11502_BETA
License type: Beta License
License expiration: 2014-10-05 10:10:00
License file: C:\ProgramData\slickedit\19\slickedit.lic

Build Date: September 29, 2014
Emulation: Brief

OS: Windows 7 x64
OS Version: 6.01.7601  Service Pack 1
Memory: 55% Load, 4554MB/8150MB Physical, 5710MB/16298MB Page File, 259MB/8388607MB Virtual
Shell Info: C:\Windows\system32\cmd.exe /q
Screen Size: 1920 x 1200

Project Type: ISeries Xpf
Language: .C (C/C++)

Installation Directory: c:\Program Files\SlickEdit\beta\ (non-removable drive,NTFS,123650MB free)
Configuration Directory: C:\Users\bej\SlickEdit\19.0.0\ (non-removable drive,NTFS,123650MB free)
Spill File: C:\Users\bej\AppData\Local\Temp\$slk.5368 (non-removable drive,NTFS,123650MB free)

I don't have have any problems with SlickEdit 18.0.1 opening and closing this file. I can't provide you with the actual file. It's a normal C++ text file however. Let me know if there's any additional data that I should try to capture.

[Lee]

Can you capture a dump file for the crash and post that or submit through support?  That would help. I can post instructions on how to capture one if you need.

[jnairb]

Yes, please let me know how to capture the dump file or whatever you need.

[Lee]

If you have Visual Studio installed, you can attach to the SlickEdit process (vs.exe) and then try to reproduce the crash.  Once it has broken, there is an option under the Debug menu to Save Dump (depending on which version of Visual Studio).   

You can use Windows Task Manager, find vs.exe (if it hasn't already closed out) in the Processes list and right-click and Create Dump File.

Dump files can be large even zipped, so you may want upload it through customer support site (http://support.slickedit.com/).

[jnairb]

I re-created and uploaded the dump (vs-dump.zip) to http://support.slickedit.com under case# CAS-66326-V362.

[Lee]

Thanks, file received.  How is your layout configured when this happens?  Could you post a screenshot of what tool windows are opened/docked and how the files are displayed.

[jnairb]

I'm attaching a screen shot of my SlickEdit window before the crash. Initially, I also had a toolbar showing, but somehow I lost that when I was trying to get SlickEdit to start w/o loading the file that causes it to crash. (If I just exit SlickEdit without closing the file first, it doesn't crash. Since I did that, it opens with that file and the project I was using, causing it to crash if I try to close that file or close that project.)