Quote from: matrix961 on June 29, 2014, 11:53:24 PM

Quote from: Jojatekok on June 29, 2014, 06:20:00 PM

Monero Client v0.27.0 has been released!
https://github.com/Jojatekok/monero-client/releases/tag/v0.27.0

Another day, an other release!

The immersive development of the Client continues with an unexpected feature: Backup Manager. It is a new solution for managing wallet backups easily without the need for any external tools. And this is only the basic functionality: many other fixes and improvements will be coming soon... Wink

Oh, and I finally implemented a crash report logging system which automagically appends each new unhandled exception to '\CrashLogs.txt'. If you experience any issues, please send that log to me if possible, it helps a lot.

For passionate people who would like to translate the Client, here is the link: https://www.transifex.com/projects/p/monero-client/ Cheesy

Thank you!

The only new bug I know about in this release is related to the newly added feature, and doesn't do any "real harm": The backup manager's restore application method doesn't reset simplewallet.exe's arguments, thus, if a new wallet has been created during the Client's startup, old wallets cannot be restored - but only in that session.

I started having crashing on start up during sync with version .26. It's doing the same thing in this version, below is the only thing in the CrashLogs.txt. I didn't experience this in testing before .26. I started it up again and it finished syncing without issue. Then it crashed again (Same Error as below) just sitting there with no other transactions coming in. I like how the transaction notifications popup as they come in now tho. You really seem to be moving everything along at a fast pace now, keep up the great work

CrashLogs.txt:
The operation has timed out
   at System.Net.HttpWebRequest.GetResponse()
   at Jojatekok.MoneroAPI.Helper.GetResponseString(HttpWebRequest request)
   at Jojatekok.MoneroAPI.RpcManagers.RpcWebClient.HttpGetData[T](RpcPortType portType, String command)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers()

Quote from: heslo on June 30, 2014, 04:13:23 AM

0.27 still crashing for me Sad

Thank you for the crash logs! I finally have an idea why it happens (2 or 3 minutes) after startup: One of the recent versions introduced automatic blockchain saving through the RPC every 2 minutes, and that can take more than 30 seconds (which is the WebRequest timeout I was using). I have set the timeout to Timeout.Infinite, as local requests may take any seconds. The reason why I didn't encounter this issue is that I am using an SSD, thus, my read/write times are faster than in the case of HDDs. (Probably, that's the reason behind TheNobodies' server being able to handle the situation without crashing.)

Also, I made the blockchain save only every 5 minutes instead of 2, but the wallet will still save every 2 minutes (as that's a lightweight operation compared to storing the blockchain).

EDIT: The new version will also feature better Timer handling. Instead of waiting for a pre-defined interval (see above on the graphics), requests are going to be finished before (see below).

The 't's are the Timer's interval