The memory could not be read - KiTTY login

Jamie Maxwell - Fri 27/05/2016 11:06:29 CEST +0200

Hello,

We have just recently started using KiTTY portabale as an alternative to PuTTY as we can lockdown the 'close window x' option.

We initially were running version 0.66.6.1p but some users were reporting issues and sending screenshots showing the error:

'SSH, Telnet and Rlogin client has stopped working

A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.'

Every time this was reported with a screenshot it showed that it only happened when a user had launched the program successfully then typed in their username and password.

As our version was a little out of date, we then upgraded to version 0.67.0.3p. After the file was replaced with the newer version, we started to receive reports that users were receiving a new error at the exact same spot (ie after typing in username and password). The error they are now receiving is:

'The instruction at 0x004a4f02 referenced memory at 0x32363135. The memory could not be read.

Click on OK to terminate the program.'


We are running KiTTY portable from our shared CIFS drive as this allows us to easily give 20+ users access to the executable and allow us to upgrade easily. This is how we have been using PuTTY for some time as well.

Any help would be much appreciated.

Regards,
Jamie

Venkat Ram - Fri 27/05/2016 12:10:11 CEST +0200

I face the same issue with a different memory location. I've started using Kitty quite a few days back. First i thought its my windows since i reimaged recently but ssl works with PuTTY for the same device. @Developer, you quick solution is much appreciated.

Regards
Venkat

Cyd - Fri 27/05/2016 19:10:47 CEST +0200

First try to disable password auto-store.
Add
     [KiTTY]
     userpasssshnosave=no
to your kitty.ini file.

Then send me a memory dump (http://www.9bis.net/kitty/?page=Savedump), just after typing the password, or just before if it crashes again.

Matthew Yauch - Tue 31/05/2016 20:11:47 CEST +0200

Hello,

I had this issue as well only on specific devices (the same switches would crash 95%+ of the time).
I renamed Default%20Settings to Old. The issue no longer occurred on the new Default%settings that was auto-generated.
I performed a Diff on the two files and went through each line of changed config.

I found that changing TermWidth\ to anything greater than TermWidth\ crashed it. Works on 95, 96+ crashed it for me.

Every other line in the configuration that had been changed by my customized setup did not crash it.

Matthew Yauch - Tue 31/05/2016 20:13:24 CEST +0200

Comment submission stripped out the lines of config.

TermWidth \ 80 \ is default
TermWidth \ 95 \ up to 95 does not crash for me
TermWidth \ 96 \ and above does crash for me

Leo - Sat 11/06/2016 13:58:31 CEST +0200

It seems the last beta build fixes the issue: http://www.9bis.net/kitty/data/beta/kitty.exe
... maybe for the next official release.

James Olsen - Wed 31/08/2016 17:25:58 CEST +0200

Latest version (at time of writing) is 0.67.1.4p, and I have a server I can connect to that crashes putty every time after I enter the correct password. The beta linked in previous comment also crashes (I assume it predates 67.1.4 anyway).

I get the following message from KiTTY about the crash:
"Instruction at 0x00000000004A5626 referenced memory at 0x0000000039306233. The memory could not be read."

If I choose to debug it (Visual Studio), the message in there is slightly more descriptive: "Unhandled exception at 0x004A5626 in kitty_portable.exe: 0xC0000005: Access violation reading location 0x39306233."

Changing TermWidth did not seem to work around the issue (it still happens even with widths less than 95).

Lolo M - Mon 05/09/2016 11:29:47 CEST +0200

Hi guys,

i have the same problem, i have figured out that issue appears only when my computer uses more than 4Gb of memory.
So when my computer run with 3GB used, my kitty is working fine. When i reach the 4Gb, the soft crashes at the prompt all the time with differents devices.
So currently cleaning some other program is my only workaround.
The problem appears only with SSH connections.

Mikhail - Tue 27/09/2016 15:54:00 CEST +0200

Hi.

i have the same problem :(
Version 0.67.1.4
Open only two stored ssh sessions.
When open new ssh to cisco - after input password have crash.

tester1 - Fri 14/10/2016 10:27:50 CEST +0200

I guess the problem is related to the color settings in the default settings file

Colour20\245,222,179\
Colour19\255,215,0\
Colour18\255,160,160\
Colour17\255,85,255\
Colour16\255,222,173\
Colour15\135,206,235\
Colour14\205,133,63\
Colour13\255,255,85\
Colour12\240,230,140\
Colour11\85,255,85\
Colour10\152,251,152\
Colour9\255,85,85\
Colour8\255,43,43\
Colour7\85,85,85\
Colour6\77,77,77\
Colour5\0,255,0\
Colour4\0,0,0\
Colour3\85,85,85\
Colour2\51,51,51\
Colour1\255,255,255\
Colour0\255,255,255\

When I restore the default values everything works without the memory problem

Barm - Thu 20/10/2016 14:44:40 CEST +0200

The same on newest version 0.67.3.1 :
This instruction at 0x004b19f6 referenced memory at 0xbffb2957.
The memory could not be read.

Bonzo the Fifth - Fri 21/10/2016 04:08:10 CEST +0200

I'm having the same memory issue as well. I don't normally have this when I open kitty with a fresh restart, but if I open it later, the liklihood increases for failed sessions (always random, never the same environments). My suspicion is that Lolo M may be correct that it's related to the RAM allocation state in that particular moment (hence why it seems these crashes occur in intermittent clusters).

To be on the safe side, I've restored the default settings as well, just to eliminate that troubleshooting step. It doesn't seem to have made a difference, even when I take a fresh install and manually enter the environment settings, I get the same 'referenced memory' errors seemingly at random.

Thank you for your help and let us know if we can help in any way.

TiM - Wed 09/11/2016 03:10:22 CET +0100

Glad this isn't just me.
This is a very annoying bug and has caused me to go back to PuTTY for anything I need to know will work 100%
Hope it can be sorted soon, let me know if I can provide any useful debug.

nomoo - Wed 09/11/2016 10:59:18 CET +0100

Same here. Version 0.67.3.1.

noname - Mon 14/11/2016 10:16:01 CET +0100

Same here 0.67.3.1. @2/11/2016, can confirm the 3Gb RAM theory. It works fine when I have until 2,8Gb used. Few more chrome tabs and the kitty dont work again.

Mark - Tue 15/11/2016 20:29:44 CET +0100

So far, I've had good luck with the following:
1) Create a shortcut to KiTTY
2) Right click the shortcut and go to the Compatibility tab
3) Check the "Run this program in compatibility mode for:" box and select "Windows XP (Service Pack 3)"
4) Start KiTTY via the shortcut

I'm using Windows 10 Enterprise.

Andre - Wed 23/11/2016 22:03:56 CET +0100

I've tried the last 3 versions of Kitty .... always the same memory errors, really annoying...

zener - Wed 07/12/2016 00:12:07 CET +0100

Mark: GREAT! I can confirm that the compatibility mode (WXP SP3) seems to be working. Finally!

Bonzo the Fifth - Thu 08/12/2016 06:45:07 CET +0100

Out of curiosity, I decided to try the kitty build with the zmodem functionality removed. I haven't had a crash since then, but know that, alone, isn't enough evidece to say if this is a possible culprit.

If anyone wants to give it a shot and see if it works for them, here's the link to that variant: http://www.9bis.net/kitty/data/beta/kitty_nozmodem.exe

Chot - Fri 09/12/2016 01:56:07 CET +0100

Setting it to XP compatibility mode requires you to hit that UAC dialog each time you open kitty.
If you are experiencing this problem when running Windows 10 64bit, simply set it to Windows 8 compatibility mode and it will work aswell.
However, instead you'll still be using the modern widgets and won't be annoyed by UAC.

Cyd - Wed 14/12/2016 23:37:36 CET +0100

Can you test this build: http://www.9bis.net/kitty/data/beta/kitty.exe
with this setting (in your kitty.ini configuration file):
[KiTTY]
userpasssshnosave=yes

Bonzo the Fifth - Wed 21/12/2016 05:32:59 CET +0100

Using the test build and the .ini setting, it seems that the memory errors decrease, but don't quite go away.

It does seem to be occurring more reliably with specific environments, now, though that could just be a coincidence.

Is there other troubleshooting I can do? A log or something I could generate which might help with troubleshooting further?

Gerald - Wed 28/12/2016 21:10:38 CET +0100

userpasssshnosave=yes works for me with KiTTY Portable 0.67.3.3p @ 18/12/2016 and finally gets rid of this annoying problem.
Losing the "duplicate session" feature is a bit of a bummer though.

Bonzo the Fifth - Fri 30/12/2016 05:49:33 CET +0100

Just tried the new beta build 0.67.3.3 in the "0.67.3.3 always read-faults when connecting" thread. That appears to have done the trick!

Thank you so much for you work on this!

Warren - Tue 03/01/2017 18:37:49 CET +0100

Using the beta build and userpasssshnosave=yes but I'm still receiving "The instruction at 0x771443df referenced memory at 0x632e6873. The memory could not be read."

Warren - Tue 03/01/2017 18:58:19 CET +0100

The kitty_nozmodem.exe version works for me

Sam - Thu 19/01/2017 12:23:31 CET +0100

Same problem here, only Compatibility mode helps (XP3) on W7.
When I start kitty without compatibility mode, it appears with a green frame around the dialog window, whatever it means - see https://postimg.org/image/t3mf8ivnh/b23942b4/.

I've also found, that new kitty has problems to create files or directories sometimes. If i delete kitty.ini it is not recreated, but when I try older version 0.66.6.1p - this seems to be also the last version, that works without problems for me.

Cyd - Thu 19/01/2017 14:12:32 CET +0100

I'm trying to guess what KiTTY modification is involved into this issue.
Can someone test these special build and tell me which works and which fails.
Thanks

kitty_noadb
kitty_nocapi
kitty_nocygwin
kitty_nohyperlink
kitty_noimage
kitty_nokeymapping
kitty_nolauncher
kitty_noportknock
kitty_noprintclip
kitty_noputtyx
kitty_noreconnect
kitty_norutty
kitty_nosavedump
kitty_nostart
kitty_notutty
kitty_nowincrypt
kitty_nowts
kitty_nozmodem

Petr - Tue 31/01/2017 10:35:13 CET +0100

All those 18 special builds crashing for me.

It doesn't crash only with "userpasssshnosave=yes" in kitty.ini (but I'll test it more thoroughly as those crashes are quite random so there are times when it doesn't crash even without that setting.

Cyd - Fri 03/02/2017 13:53:11 CET +0100

Finally I've found the light. Thanks to Petr that help me to reproduce the issue on fresh new Clear Linux install.
Here is a new beta build: http://www.9bis.net/kitty/data/beta/kitty.exe
Can you test it to check if the issue is gone definitely.

Answer

The forum is actually closed