Chat history should be saved on a timer and on shutdown.

This is still an issue in Spark 2.5.5.

This is still an issue in Spark 2.5.8. It seems like chat history is very iffy...sometimes it remembers, but more often than not, history gets lost. This is a critical feature. History should be saved whenever a line is added. Strategies can be imployed to keep this from slowing chat down.

Yes, I can confirm that this is still an issue in 2.5.8.

IMHO the only robust solution would be to save history when created (i e when the message is sent), and I can't understand why it isn't done like that from the beginning, is it a performance issue?

Hi John. It was for performance reasons. I was in the process of rewriting the history part of Spark, but I moved on to another job. It's quite simple to redo that part, and I think there are some takers these days to do just that. Instead of every single message, I would recommend persisting on a very short timer and pulling messages from a queue.

Yes, this should be a high priority. For any business it is critical to have a reliable history - that does not get lost!

Agreed, saving the history is critically important!

Losing history is a silly mistake, this is the only reason stopping me using this IM client.. Please fix!""

When you get as many messages as me, I cont keep track of them all, so chat history is very helpful when it logs it. Sometimes it does & sometimes it loses loads!

A print button would be great too! Especially if someone else closes all your messages on your pc when you are not using it!

I changed to Spark from another Jabber client because its history saving was unreliable. Unfortunately, Spark is just as bad. If you close the application without first closing all the tabs manually, none of the messages are saved. Closing all the user tabs first seems to save OK, but users cannot always be relied on to do this.
The rest of the program works fine, so please fix this major bug!

just to comment, i have never seem such a problem with Spark myself, and i cant reproduce it while closing chat window with all tabs altogether. It saves the history for me.

this is probably fixed in this patch http://www.igniterealtime.org/community/thread/35795 (27-29 messages), anyone can try spark.jar uploaded there. it is sving history even on Spark crash.