1748163 Members
3626 Online
108758 Solutions
New Discussion

Re: Putty fatal error

 
SOLVED
Go to solution
coollllllllllll
Regular Advisor

Re: Putty fatal error

Yaa from the same machine.
Dennis Handly
Acclaimed Contributor
Solution

Re: Putty fatal error

>Yaa from the same machine.

 

Perhaps you need to restart it?

Task manager says my putty.exe is only taking 3.8 to 4.5 MB each.

How many scroll lines to you have?

coollllllllllll
Regular Advisor

Re: Putty fatal error

Hi Dennis,

 

 

Scroll lines size is 2000000000

 

Patrick Wallek
Honored Contributor

Re: Putty fatal error

>>Scroll lines size is 2000000000

 

You're really trying to keep 2 BILLION lines in the scroll back buffer?  That seems very excessive and, depending on how many lines you are actually storing in the buffer for each terminal, possibly the reason you are getting out memory errors.

 

I would try setting that value to something much more reasonable, like 10000, and see what happens.

coollllllllllll
Regular Advisor

Re: Putty fatal error

Hi Patrick ,

 

What can be the max permissible size ? 

Because sometimes we need to refer above lines , during our batch job sessions  every night.

 

Dennis Handly
Acclaimed Contributor

Re: Putty fatal error

>What can be the max permissible size?

 

It depends on the number of putty sessions and how many lines are saved.

Have you looked at putty.exe in Task Manager to see how much memory is being used?

 

(Of course if the lines are saved in a file, then the size won't matter for memory usage, depending how window scrolling works?)

 

>Because sometimes we need to refer above lines, during our batch job sessions every night.

 

Batch jobs typically don't go to a session stdout/stderr, they go to a file.  If in a file, you can use your favorite editor to look at them.

 

Or you could use script(1) to record everything in a file and then cut the scroll lines to a smaller value.

 

Oh, putty also has logging.

coollllllllllll
Regular Advisor

Re: Putty fatal error

Hi Dennis and Patrick ,

 

Thanks scroll lines was the culprit.

Reduced to 200000 now , until now all fine.