Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash at startup on new 0.57 version #33

Closed
weggetor opened this issue Oct 28, 2016 · 5 comments
Closed

Crash at startup on new 0.57 version #33

weggetor opened this issue Oct 28, 2016 · 5 comments

Comments

@weggetor
Copy link

weggetor commented Oct 28, 2016

Hi Rick,
program crashes at startup now. Windows-Eventlog:

Anwendung: MarkdownMonster.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.IO.IOException
bei System.IO.__Error.WinIOError(Int32, System.String)
bei System.IO.Directory.DeleteHelper(System.String, System.String, Boolean, Boolean)
bei System.IO.Directory.Delete(System.String, System.String, Boolean, Boolean)
bei MarkdownMonster.ApplicationConfiguration..ctor()
bei MarkdownMonster.mmApp..cctor()

Ausnahmeinformationen: System.TypeInitializationException
bei MarkdownMonster.mmApp.get_Configuration()
bei MarkdownMonster.App..ctor()
bei MarkdownMonster.App.Main()

I tried to uninstall completely and had some trouble with glyphicons-halflings.ttf which was blocked by Windows but finally I solved this so no settings in AppData and no files in "Program Files" were left. Then fresh install but that does not solve the crash issue. So I leave it up to you

@RickStrahl
Copy link
Owner

Hmmm... Theres been a change to rename the %AppData%\West Wind Markdown Monster to %appdata%\Markdown Monster for consistency across the various folder names. I wonder why the delete of the folder would fail - should have full permissions in that folder.

Anyway - I've added a Try/Catch block around that code and I'm logging it out now to see if it happens elsewhere.

The downloads been updated.

@weggetor
Copy link
Author

Still crashes:

Anwendung: MarkdownMonster.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.NullReferenceException
bei MarkdownMonster.mmApp.Log(System.String, System.Exception)
bei MarkdownMonster.ApplicationConfiguration..ctor()
bei MarkdownMonster.mmApp..cctor()

Ausnahmeinformationen: System.TypeInitializationException
bei MarkdownMonster.mmApp.get_Configuration()
bei MarkdownMonster.App..ctor()
bei MarkdownMonster.App.Main()

@RickStrahl
Copy link
Owner

Hmmm... where are you installing from? The Chocolatey package has not been updated - the main download link here:

https://markdownmonster.west-wind.com/download.aspx

has the latest (0.57.2)

I can't duplicate the failure and I've updated a few different machines.

Also looks like the crash is not getting into the log and forwarding to the bug logging service. Is the crash getting to the error dialog or is it hard crashing the application (ie. straight into the Windows error dialog).

if you still have problems you can try this: Delete or rename the %appdata%\West Wind Markdown Monster folder if you have it and (optionally) manually copy the content into your %appdata%\Markdown Monster folder.

If there is still a problem though I'd love to find out what's causing it - cause a startup crash really sucks...

@weggetor
Copy link
Author

Was the newest version, but manually renaming the "West Wind Markdown Monster" folder did the job - no more exceptions and the others isues are also gone. Search & Replace is working and downloading post from my blog with special chars in password works again also. Good job Rick and thank you for your help!

@RickStrahl
Copy link
Owner

What does the version number show for you? It should 0.57.2

Yeah that is really odd - the code that deals with the 'update' moving of the old settings files is fenced inside of a try/catch (after your initial report) so that shouldn't trigger an exception worst case it should just fail and continue (but create a log entry). I really would love to find out why that was failing. Was there any more info in the log file (like line numbers after the second error you sent?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants