MatterControl 1.1.1 crashes on Startup

[krolco]

This happens for me on Windows 7 Home Premium running on a Mac mini running Bootcamp.

It looks like it gets one paint of the UI, and then it crashes, going off to the Windows error handler.

I had to downgrade back to 1.1.0 to get running again.

What branch/commit is 1.1.1 built from? There isn't a git branch for it.

[larsbrubaker]

I did not make the 1.1.1 branch yet (got sick on Wednesday). If you get development branch it will be the right build (and I will make the 1.1.1 branches today).

Any insights you get will be greatly appreciated.

[krolco]

I have a litte bit more information; trying to get even more.

This only seems to occur when starting up MatterControl and the printer is already on: it might be related to the autoconnect.

From the Windows reliability history, I got this:

Source
MatterControl

Summary
Stopped working

Date
‎6/‎9/‎2014 9:28 PM

Status
Report sent

Description
Faulting Application Path: C:\Program Files (x86)\MatterControl\MatterControl.exe

Problem signature
Problem Event Name: CLR20r3
Problem Signature 01: mattercontrol.exe
Problem Signature 02: 1.1.1.0
Problem Signature 03: 53850ae3
Problem Signature 04: MatterControl
Problem Signature 05: 1.1.1.0
Problem Signature 06: 53850ae3
Problem Signature 07: 37d
Problem Signature 08: 0
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Extra information about the problem
Bucket ID: 54944283

---

Trying to get better info (like a call stack)

[larsbrubaker]

Hey Monty.

I think we fixed this in the development version. We will try to get a Mac
build created tomorrow and push it up to development.

Thanks for looking into this.

Lars.

On Monday, June 9, 2014, Monte Krol notifications@github.com wrote:

I have a litte bit more information; trying to get even more.

This only seems to occur when starting up MatterControl and the printer is
already on: it might be related to the autoconnect.

From the Windows reliability history, I got this:

Source
MatterControl

Summary
Stopped working

Date
‎6/‎9/‎2014 9:28 PM

Status
Report sent

Description
Faulting Application Path: C:\Program Files
(x86)\MatterControl\MatterControl.exe

Problem signature
Problem Event Name: CLR20r3
Problem Signature 01: mattercontrol.exe
Problem Signature 02: 1.1.1.0
Problem Signature 03: 53850ae3
Problem Signature 04: MatterControl
Problem Signature 05: 1.1.1.0
Problem Signature 06: 53850ae3
Problem Signature 07: 37d
Problem Signature 08: 0
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Extra information about the problem

Bucket ID: 54944283

Trying to get better info (like a call stack)

—
Reply to this email directly or view it on GitHub
#41 (comment)
.

[krolco]

Awesome, thank you!