Random crash

[GoogleCodeExporter]

Random crash.

Might be related that I'm dealing with a script that temporarily disables ssh 
access and disconnects me... sometimes I reopen the connection and sometimes I 
leave it blank.

The "close program" dialog has this information:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name: QuTTY 0.5-beta.exe
  Application Version:  0.0.0.0
  Application Timestamp:    51c7e0c1
  Fault Module Name:    QuTTY 0.5-beta.exe
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp:   51c7e0c1
  Exception Code:   c0000005
  Exception Offset: 000da8e7
  OS Version:   6.1.7601.2.1.0.256.4
  Locale ID:    1033
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Original issue reported on code.google.com by [email protected] on 2 Jul 2013 at 4:45

[GoogleCodeExporter]

Sorry to hear about the crash.
Unfortunately current releases don't have any crashdump support.

But google-breakpad has been integrated(rev#bfd6497b602b), and future 
releases(0.6-beta) will create a minicrashdump (in c:\dumps\). This can be used 
for further analysis.

In the meantime, pls answer the following to help understand the scenario 
better.
1. How many times have you experienced qutty crash
2. How much time was qutty running before crash.
3. Do you remember of any specific operation that triggered the crash, like 
opening a new tab, right-clicking on a terminal, etc.
4. Do you heavily use 'Duplicate to Tab/HSplit/VSplit' keyboard shortcuts. If 
so I recently fixed an issue that can lead to crash.

I faced a similar crash as well, but not able to repro it.
Let us know of any specific way to repro it, if you happen to hit it.

Thanks

Original comment by [email protected] on 2 Jul 2013 at 6:12

• Changed state: Accepted

[GoogleCodeExporter]

1. it has crashed 3 times now
2. it was running around 3 hours-ish.
3. no specific operation triggered it. each time qutty was actually in the 
background when the crash occurred. I had 2 tabs open to 2 different servers, 1 
was connected and 1 had just recently died (due to the script i was testing 
that killed sshd on the server)
4. each time there were 2 tabs open. I use duplicate to hsplit a bit for 
opening a log view, but it was not currently open at the time (it had been 
earlier in the morning)

I'll let you know, but repro is hard as it occurs in the background.

Original comment by [email protected] on 2 Jul 2013 at 6:18

[GoogleCodeExporter]

Okay. Not able to guess anything here.

Our best bet is to wait for the 0.6-beta release (I expect to be in this 
weekend) with crashdump support.

I am sure this is due to the recent codechanges (between 0.4-beta & 0.5-beta). 
I will take closer look at them as well.

Original comment by [email protected] on 2 Jul 2013 at 6:57

[GoogleCodeExporter]

hi Nick

The next release is being delayed by a few days (or a week).
Have you experienced any further crashes. If so are they also running 3 
hours-ish.

Thanks

Original comment by [email protected] on 9 Jul 2013 at 5:18

[GoogleCodeExporter]

No further crashes but I've no longer been testing on those servers. Perhaps 
the issue is related to connection killed by host, or reconnect?

Original comment by [email protected] on 9 Jul 2013 at 2:15

[GoogleCodeExporter]

Ok. Thats good to know.
I will try to repro by killing sshd.

Original comment by [email protected] on 9 Jul 2013 at 6:07

[GoogleCodeExporter]

It still took a while to crash after killing the network service... it always 
happened in the background and usually while 1 connection was reopened and the 
other was not reopened.

Original comment by [email protected] on 9 Jul 2013 at 6:10