Roger Meier's Forums

Hi,

I get the error below immediately after sending text files over serial. All details below.
This occurs with any of the files I tried which were all about 8 - 14KB in size.
Same issue on 4 different Macs with the same setup and same files.
Using an FTDI USB-Serial adapter and FTDIUSBSerialDriver_v2_2_18.

EDIT: Some extra info about the versions of MacOS: One runnning 10.8.5, two running 10.7.5 and one running snow leopard 10.6 all had the problem. However a fifth Mac running 10.7.5 does not get the error message and seems fine.

Any advice on resolving this would be very much appreciated. Let me know if any further information is required.

I read the following Bugfix listed in the ReadMe for v1.4.2 - is this the same issue that I am experiencing?
- fixed bug that would cause a NilObjectException in the Xmit routine in cases where the serial port is still transmitting or is hung while the port goes out of scope. This hopefully fixes the crash bug some users have experienced on occasion.

Date: 2013-10-14 21:21:34
Exception Type: NilObjectException
OS: Mac OS 10.7.5
App Name: CoolTerm
App Version: 1.4.2 (Build 201)
App Build Date: 2013-02-17 14:53:31
System ID: F0:B4:79:15:88:6A

Open Terminals:
FTF CoolTerm.stc
PortOpen = True
Port = usbserial-FTF00001; BaudRate = 2400; DataBits = 8; Parity = N; StopBits = 1; FlowControlCTS = false; FlowControlDTR = false; FlowControlXON = false; DTRDefaultState = true; RTSDefaultState = true; LoopbackRXData = false; IgnoreRXSignalErrors = false; RXBufferSize = 10000; CaptureFormat = Raw; CaptureTimeStamp = false; CaptureWaitForTerminationString = false; CaptureTerminationString = 0D 0A; CaptureRetainTerminationString = false; CaptureLocalEcho = true; CaptureFileStaysOpen = true; TerminalMode = Raw; EnterKeyEmulation = CRLF; EnableBell = true; LocalEcho = true; ReplaceTAB = false; TABSpaces = 4; ConvertNonPrint = true; EnableBackspace = false; TerminateSendString = false; TerminationString = 0D 0A; TXCharDelayEnabled = true; TXCharDelay = 20000; TXLineDelayEnabled = true; TXLineDelay = 20000; TXLineDelayChars = 0A; XmitWaitEnable = false; SendTextSoundEnable = true; TXPacketSize = 256; ViewerMode = Plain; AutoConnect = true; AutoDisconnect = true; WindowPosition = 221,198,688,480

Call Stack:
Sub winTerm.winTerm.txThread_Run( winTerm.winTerm, TransmitThread )
Sub Delegate.IM_Invoke( TransmitThread )
Sub AddHandler.Stub.0()

Thanks for posting this. The log you posted is not exactly the same as the anonymous ones I received through the feedback system, but this may very well be related to the same issue.

I have recently released v1.4.3 where I made a few changes to the transmit thread code. Can you give the latest version a try and see if the issue persists since it seem you have a way to consistently make it happen.

In case it does happen with v1.4.3 also, please post back. I would then like to send you a debug build with some data logging enabled so that I can get a better idea where exactly this is happening (please send me your e-mail address to support@the-meiers.org).

That's great - thank you.
1.4.3 seems to resolve the problem at least on the Mac I have managed to test on so far. I will try the others and report back here if the error recurs.

One note - I have ticked option to play notification sound after sending text file. When I open the program, everything works as usual. (no sounds when I enter keystrokes). But after sending a long text file, the notification sound is played and thereafter every time I press any key, I also hear the ping.
This is not causing me any problem, but I thought I'd mention it in case you are interested to know.

Thanks. I'm glad 1.4.3 works for you. Thanks also for reporting the bug with the notification sound. I will try to replicate on my machine. Does this only happen with large files, or with small one also?