Crashes on first run (Windows 10)

[Bruno Dery]

I downloaded the Browser Chooser 2.exe release 2 and tried to run it many times but it crashes right away (on Windows 10). Also tried to run as administrator; didn't work either.

[David De Sloovere]

Also getting an instant crash here.

Browser Chooser 2.exe is version 2.0.4.36947

Windows 10 version is 1709 (OS Build 16299.248)

[Stimpy]

Got the same problem on WIndows 10 Home (Latest version) and all Net Framework versions are alright according to Microsofts own checker tool.

Event Name: CLR20r3

P1: Browser Chooser 2,exe P2: 2.0.4.36947 P3: 5aa1e3f7 P4: mscorlib P5: 2.0.0.0 P6: 59a72025 P7: 34ad P8: 119 P9: System.IO.DirectoryNotFound

EDIT: Solved it by copying "BrowserChooser2" folder (and "BrowserChooser2Config.xml" file) from my other PC (it worked there) to "Appdata\Roaming" on the PC where it didn't work.

EDIT2: Got NET exception crash when scanning for browsers due to the program not being able to (seems like it has to do with access rights) extract the icon of the browsers. My solution was to use a program to extract the icons and put them in the "Browser Chooser 2" folder which is located in a folder on C: due to it otherwise crashing. Then choosing to use custom icon and use the extracted icon.

[guy]

Can you provide more details such as the call stack found in the 'details' button of the crash dialog.

You can also run BC2 with the --log option and provide the log file generated.

Thanks.

[Axel]

I have the same issues since a week with the latest version. Here is the log file:

"3/15/2018 1:31:08 PM","modStart.Main","Starting App" "3/15/2018 1:31:08 PM","modStart.Main","Start Processing Command Line","--log" "3/15/2018 1:31:08 PM","modStart.ContinueMain","Enable Logging" "3/15/2018 1:31:08 PM","StartupLancher.New","Start" "3/15/2018 1:31:08 PM","Settings.New (No args)","Start" "3/15/2018 1:31:08 PM","Settings.SharedNew","Start" "3/15/2018 1:31:08 PM","Settings.SharedNew","End" "3/15/2018 1:31:08 PM","Settings.New (No args)","End" "3/15/2018 1:31:08 PM","StartupLancher.New","Is 64 Bit" "3/15/2018 1:31:08 PM","GeneralUtilities.LoadDLLPrep","Start" "3/15/2018 1:31:08 PM","GeneralUtilities.LoadDLLPrep","End" "3/15/2018 1:31:08 PM","StartupLancher.New","End" "3/15/2018 1:31:08 PM","modStart.Main","Start Processing Command Line","--log" "3/15/2018 1:31:08 PM","modStart.ContinueMain","Exiting"

Any workaround? I extensively use Browserchooser and now nothing is working on any of my Windows 10 machines.

Thanks!

[guy]

That weird? Do you have the call stack from the crash dialog?

[Axel]

No, sorry, it wants to send crash information to Microsoft...

[Wayne Arthurton]

I did about 3 hours of testing and code reading tonight and I've narrowed it down to the initial write of the V5 config file. I've created a minimally usable BrowserChooser2.xml that you can put in your %APPDATA%\BrowserChooser2 (MAKE A BACKUP COPY OF ANY EXISTING FILE FIRST) or execution directory if portable and it should run. You will have to redo detection, etc.

BrowserChooser2.xml

This weekend (or during some downtime tomorrow) I will trace out the code in VB and submit a pull request.

[Axel]

Works for me, thanks a lot!!!

[David De Sloovere]

I didn't even have the BrowserChooser2 folder under AppData. Created the folder, placed the xml file there, now browserchooser starts up! Now I have to configure it correctly.

[Bruno Dery]

Thanks, that did the trick for me too.

1- create the folder BrowserChooser2 in AppData

2- put the BrowserChooser2.xml in there

Thanks, from a quick look, I like what I see so far... :-)

[Wayne Arthurton]

I'm still trying to get my personal VS development environment up. I should not do it on my work computer.

Hopefully tonight.

[Wayne Arthurton]

I have submitted pull request #3 to solve at least one cause of the crash.

[guy]

Please try https://browserchooser2.com/app/33/Browser%20Chooser%202.exe to see if this fixes your issue. If yes, I will push it to release.

[Wayne Arthurton]

I will test that update tomorrow AM.

I did some work tonight on removing the embedded compiled dlls.

I accomplished this by:

• Adding the source for IconPack and SepCombo.
• For SHDocVw I added a reference to C:\windows\syswow64 (yes I know it is 64 only right now but I"m still working on it) instead of the Interop.SHDocVw in resources.
• I was able to remove the serializer reference as well (Create Serialization Assemblies in Advanced Compile set to Auto) .
• I've had to temporarily comment out the OSVersion.dll as the source gave some clr violations.

• The assemplies / Interops are compiled to the bin directory giving you Browser Chooser 2.exe, InteropSHDocVw.dll, TAFactory.IconPack.dll, and SepCombo.dll.

• Then I run ILMerge with those files and create and output of BC.exe (again temp name while testing) giving you a portable exe.

The startup speed seems to be increased significantly over the previous dll embedding. It also removes the need to extract the dlls.

If I then run ngen.exe over the BC.exe I can further reduce my startup time.

This is very rough and I am sure has some issues to work through (32bits, os version checking, currently I'm using a .net35 target, etc).

I'll commit a branch with the changes to my fork tomorrow if you'd like to see what I'm doing.

[guy]

Please do. Let's track it as a separate issue. I can't find any way to split an issue here.

[Wayne Arthurton]

I haven't forgotten this. I need to fix a couple of things with the code before I send.

[Kevin Bushman]

Hey there, I ran into this problem as well. Here's the error from the event log.

The build you provided above is working for me though. Thanks!!