slickedit crashes on startup

[Graeme]

The second time I ran slickedit I got a weird empty titleless dialog in the middle of the screen that wouldn't close but disappeared when I minimised it.  The third, fourth and fifth times I ran slick it crashed at startup "slickedit has stopped working, Windows is checking for a solution".  Any suggestions?  Could it be trying to run some of my V18 macro files which I have now rebuilt with V18  - which maybe aren't compatible with V19?

[Dennis]

How about collecting a mini-dump when it crashes and sending it in?

You could also try starting SlickEdit with a clean configuration directory.  This would ascertain if the problem is with migrating settings or macros from v18. 

vs +new -sc C:\Temp\newconfig\

If it has to do with migrating from v18, it would be good if you sent the old (18.0.1) configuration directory into support so we can replicate the problem.

[Graeme]

How do I create a mini-dump?

[Graeme]

Found procdump  - is this how to do it?  Where do I send the minidump and my configuration folder?

Code: [Select]

c:\GP\tools\SysInternals>procdump -w vs.exe -t

ProcDump v7.0 - Writes process dump files
Copyright (C) 2009-2014 Mark Russinovich
Sysinternals - www.sysinternals.com
With contributions from Andrew Richards

Waiting for process named vs.exe...
...

[19:49:07] Unhandled: C0000005.ACCESS_VIOLATION
[19:49:07] Dump 1 initiated: c:\GP\tools\SysInternals\vs.exe_140823_194907.dmp
[19:49:08] Dump 1 complete: 38 MB written in 0.1 seconds
[19:49:08] Dump count reached.


[Graeme]

If I repeat the process of migrating my V18 config folder (a copy of) I can't reproduce the crash.  Let me know if you want the dump file and the config folder associated with it.