crash while converting 2012 data?

[ChuckInDodgeville]

I installed beta 3 and launched it on my Win7 machine.  It began converting my files from SlickEdit 2012 (v17.0.3.0 64-bit).  It seemed to crash out before completing.  Then it seemed to come up OK when I launched it again.  It sent me through the setup wizard again.

This doesn't seem to be much of a problem.  Though I didn't capture the error, I had the distinct impression that the program crashed out and I had to restart.

[Dan]

Can you delete the config/vsdelta directory and config/22.0.0 directory and let it convert again and see if you can get a mini dump?  I'm worried it crashed converting the backup history data.

[ChuckInDodgeville]

Indeed it crashes while "upgrading backup history archive files".  "SlickEdit has stopped working".  It is 36% through the conversion.  How should I get a mini-dump?

[Dan]

Can you attach the Visual Studio Debugger, and it will be under the Debug menu.

On the other hand, if you could send me the offending archive file, I could send you a DLL with some debug that would print out which file it is converting, and you could send me the one archive file.  Most of the time people can't do this.

[ChuckInDodgeville]

I will have to install VisualStudio (express?) on this machine.  Will that work?
How can I tell which is "the offending archive file"?  Is that the whole 500MB 17.0.3 directory?

[Dan]

I'm not sure if the express version has the debugger.

I would put together a special dll for you that would print out which archive it's converting.  Hopefully, the last one is the problem.  IF you'd be able to send it to me.  Most customers can't send in a source file, which I obviously understand.

[ChuckInDodgeville]

I'm missing the specification of which file is the archive.
I'm also installing VS Express 2015 desktop.

[Dan]

It will be one of the files in (config)\17.0.3\vsdelta\.

[ChuckInDodgeville]

yeah, I'm not eager to share the whole directory.  We'll see what VS Express does.  Or can you provide a DLL that shows the names of the files being processed?

Now that I look, it's clear to me that this history is a bunch of junk that I should just delete.  This isn't really a high priority.  It seems to list every file I've touched in SlickEdit for the last 10+ years I've been using it.  Most of the files no longer exist.

[Dan]

That's quite possible, but I would really like to be able to solve the problem.

How about this:  I'll send you a DLL that will write the file it is processing to vs.log.  This is pretty well tested, so it should be a problem with that specific file (I hope), not an accumulative problem.  You can look at the last file in vs.log, see what the filename is, open the file, and see if you can send it to me.

If this will work, you can PM me an email address to send the new DLL to.

[ChuckInDodgeville]

I sent the pm.

[ChuckInDodgeville]

I collected and sent the logs.

[Dan]

Chuck and I took this offline, and we have it fixed up.  If anybody else sees something like this, contact me here.