Thanks for your feedbkack Jojatekok. [...] Although, there are some visual annoyances (for example, on Windows, the whole application produces weird window behavior, there should be an epilepsy warning before doing such an operation  ) [...] I didn't noticed that. I think it depends on compilation options and embedded .dll's. The binary I linked works without glitches in a W8 virtual machine, but as I use it for personal tests, I didn't test it in more specific environments. In the future in will need to go further in compilation options and platform-dependent problems, although this is not my priority yet. Also, an "OpenGL" version can be compiled but requires GPU drivers. I am using Windows 7 SP1 x64, to be exact.  By the way, how and when will the bounty's winners be chosen? If possible, I would propose a voting by users with 20+ posts. |
|
|
|
It works well. I used it for weeks in replacement of simplewallet and it fits my needs without bugs. I mainly focused or code architecture in order to keep it flexible and future-proof. However, I keep it for devs only until more Monero Core features are implemented. (I will try to participate). If you want, you can try the version I use in my Windows 8 (x64) tests here : http://toh.neozaru.info/toh/public/bitmonero-qt-0.0.1.zipAbout the RPC-free wallet, compiling with it is a tedious task because required code is not part of official Monero repository. Thus, bitmonero-qt can still be used with simplewallet/RPC. Nice work! I see that you are very interested in a special Core concept.  You have added some great features (I didn't try them all), including custom TX fees, and I see that a deeper integration of wallet functions is your goal. Although, there are some visual annoyances (for example, on Windows, the whole application produces weird window behavior, there should be an epilepsy warning before doing such an operation ), I see that you didn't just fork another Qt wallet, but made a lot of effort towards a better future with Monero. |
|
|
|
I'd try it on my desktop PC but in the middle of a build right now waiting for parts so can't confirm. I didn't have this problem on 0.24 and below on the SP2 that's the only reason I'm mentioning it. Running http://127.0.0.1:18081/save_bc returns.... { "status": "OK" } And there's over 50GB free on the drive and just under 3GB of free RAM if that helps you any Please try Monero Client v0.28.1 which can be downloaded from here, and reverts the blockchain saving algorithm to a state when it was working for everyone. Hopefully, this will really work. |
|
|
|
Spoke too soon.... same error  The request was aborted: 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() When does it crash like that? About 5 or 6 minutes after startup? I've been trying to reproduce the issue by using an HDD as the blockchain's storage without any luck. Yep, takes a few minutes then cracks the shits and crashes. Not running this on a HDD but an SSD, it's on my Surface Pro 2 if that helps any Then, the issue is definitely related to blockchain saving through the RPC. Can you open http://127.0.0.1:18081/save_bc from your browser while running Monero Client? (It may be loading for more than a minute.) Make sure that you have at least 3 GB free on your device, just for temporary files. Also, please try running the binaries from a PC! Testing v0.28. I didn't have any instances where the gui crashes while syncing or just having it open for me. I decided to check the directory just to see if there was anything in the logs and found a crash log. I wasn't expecting that since the gui didn't crash on me. I did restart it when switching wallets and the same time stamp on the crash log matches with the time stamp in the bitmonerod log when the process finally stopped during one of the restarts.
It was the same error as previous.
I started it up again and let it sit there with no issues. Just tried to shut it down again and the client shutdown fine but wrote another crashlog with the same error right when the daemon process ended. The error is also written in the windows event viewer. Doesn't bother me since it's not happening when I'm using it now. Just thought I'd report it.
Shutdown "crashes" don't matter, so I'll implement a function to automatically ignore them from being written into CrashLogs.txt EDIT:lololol Jojatekok, I think you need to get outside more man and let your brain get away from wallet software  I'm going to be running with my friend tomorrow, but thanks for worrying about my mental health |
|
|
|
Spoke too soon.... same error The request was aborted: 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() When does it crash like that? About 5 or 6 minutes after startup? I've been trying to reproduce the issue by using an HDD as the blockchain's storage without any luck. |
|
|
|
Jojatekok,
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()
can you fix it? Definitely, here you are! Monero Client v0.28.0https://github.com/Jojatekok/monero-client/releases/tag/v0.28.0This version features a lot of fixes, most of them related to timers. It also solves some recent annoyances of the GUI, and contains more code for automatic element focusing. I hope that it resolves all of the issues! |
|
|
|
I have opened translations for anyone who wants to help contributing to the project. If your language is not yet available, but You want it to be implemented, then don't hesitate to notify me here or in PM. Dutch translation added Whoa, that's pretty interesting...  Tonight, I was dreaming about a Dutch (yeah, exactly that) translation being made. I should become a fortune teller Thanks! |
|
|
|
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).
Don't spend too much time on it. This feature will probably be fixed or removed soon. https://github.com/monero-project/bitmonero/issues/50It has already been resolved. The second picture is just a new feature for Timers, and it has been implemented too. By the way, the reason I don't yet use simplewallet is that rpcwallet is coming soon, and simplewallet's RPC functionality is not as extensive as the one in command line. EDIT: I forgot to ask: How is your Qt project going? What about the special wallet implementation? |
|
|
|
Monero Client v0.27.0 has been released!https://github.com/Jojatekok/monero-client/releases/tag/v0.27.0Another 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... 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/ 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() 0.27 still crashing for me 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 |
|
|
|
Monero Client v0.27.0 has been released!https://github.com/Jojatekok/monero-client/releases/tag/v0.27.0Another 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... 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/ 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.
|
|
|
|
No more secrets: Here is the feature I was talking about yesterday! The Backup Manager allows you to periodically back up your wallet data easily with the press of less than 5 buttons. By default, it uses your wallet backup directory (which can be set in the options), but you can also define a custom path when creating new files. Restoring backups has never been easier: You only have to select a date (or a custom path), and then press a button. The new wallet gets loaded immediately without the need for the application to be restarted. Please be patient, great things need time to be made! You have added very nice features in your wallet, but I don't see the point for this one : - If you are backuping ".keys" files, you should add a warning message because this file NEEDS to be kept secret and deleted if the computer is sold/given to another person. I think you should use electrum-like seeds instead. - For data files, they are regenerated automatically (blockchain scanning) if they are deleted. What is the use case of a backup ? However if this feature allows wallets to be saved differently (without .keys/data file), that could be a good idea because current formats are not UNIX <--> Windows compatibles. At this time, it saves and then restores every file stored in '\WalletData' to '\WalletData\Backups' by default. It allows the user to easily restore the wallet whether something goes wrong (file corruption for example), without the need to re-synchronize the wallet itself. Naturally, a future release will include electrum seed backup opportunities too. EDIT: This message will be shown before each backup:  Also - based on your kind advices - I'll add a similar warning dialog before enabling auto-backup, and have already added a placeholder button for restoring wallet data from an electrum-like seed. |
|
|
|
No more secrets: Here is the feature I was talking about yesterday! The Backup Manager allows you to periodically back up your wallet data easily with the press of less than 5 buttons. By default, it uses your wallet backup directory (which can be set in the options), but you can also define a custom path when creating new files. Restoring backups has never been easier: You only have to select a date (or a custom path), and then press a button. The new wallet gets loaded immediately without the need for the application to be restarted. Please be patient, great things need time to be made!  |
|
|
|
I too am getting the same crashes... worked fine in 0.24, but 0.25 and 0.26 both crash within a few minutes of launching the app. How can I help?
I'll look into the case, and try to write a general debugging algorithm which exports crash logs to '\CrashLogs.txt'. Version 0.25.0 featured a core change, so it's definitely possible that it could be a reason. Yesterday, I was running Monero Client all night long, but didn't encounter the bug... EDIT: The mechanism has been successfully implemented and tested (it catches all the bugs), so it is going to be deployed in the next version. |
|
|
|
May I ask whether you ran simultaneous instances of bitmonerod.exe or the Client itself
No, i dont ran simultaneous instances of bitmonerod.exe But now i got crash again.. can you try run with russian language? Btw i use windows 7 x64 Problem signature:
Problem Event Name: CLR20r3
Problem signature 01: moneroclient.exe
Problem signature 02: 0.26.0.0
Problem signature 03: 53aec043
Problem signature 04: System
Problem signature 05: 4.0.30319.19408
Problem signature 06: 5230e82b
Problem signature 07: 21b0
Problem signature 08: 61
Problem signature 09: System.Net.WebException
OS Version: 6.1.7601.2.1.0.256.1
Language Code: 1049
Additional Information 1: d5db
2 For more information: d5db7e396c31d0ed0a5a621b8c888cfd
Additional Information 3: c25b
Additional Information 4: c25b858394d9f8a58a87e12ed0823b42
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0419
If the privacy statement on the Internet is not available, check with his local version:
C: \ Windows \ system32 \ ru-RU \ erofflps.txt
 EDIT: i tested it with english language - same problem. i can show in teamviewer, but tomorrow, now time to sleep  EDIT 2: stable crashes after 10-15 minutes, i cannot run it under debugger because i dont know how to work with dotnet EDIT 3: it works on my windows server without crashes, so it is problem in my pc. I have sent you a debug build in PM, please try using it on your PC, and send me the crash reports you get. (Please take note that the file 'C:\_MoneroDump.txt' is not being appended to, but overwritten by each new crash dump, so rename the file after each crash!) By the way, on your screenshot, Monero Client seems to consume more RAM than it should (actually, even after a lot of QR code generation and in debug mode, it consumes only 50 MB for me). EDIT: There is a chance that the next version will contain something which I have not seen in any other wallets yet |
|
|
|
Thanks my translation works fine  but now i got crash:  I just ran it and left for 5 minutes, when i came i saw this I have been running Monero Client for an hour, but didn't experience one single crash. I also checked the code, but nothing should go wrong. May I ask whether you ran simultaneous instances of bitmonerod.exe or the Client itself? If not, then next time when encountering the issue, please send me more details about it, preferably the stack trace (which identifies the lines of code that are involved in the case). Thanks! |
|
|
|
Thanks my translation works fine but now i got crash: I just ran it and left for 5 minutes, when i came i saw this Interesting... It's an issue with the RPC service for sure, so only DaemonManager can be affected. I'll run the application in debug mode while I take a break, so I may be able to reproduce the symptom. Anyway, this is the most stable release yet, so it's recommended for anyone who uses my wallet. A can not keep up with you Jojatekok . But very nice to see the progress you are making! I plan on keeping my wallet as simple and stable as possible. I would like to remind people my wallet runs on linux as well (using mono). For a full featured and slik Windows wallet Jojatekoks wallet is definatly the best choice. I have made some adjustments to polish my wallet: Download v0.2.3-About dialog added (shows software versions and block height). -Changed icon (to the one from the branding kit). -Non-main windows don't show in taskbar any longer.  (versions numbers in the screenshot are wrong, this has already been fixed in the download) Thank you for mentioning my Client, it is a pleasure for me. I have to admit that the initial inspiration for me was your WinForms project, and it also seems like a viable multiplatform alternative for an official wallet GUI. It fills me with happiness and joy to meet awesome people like everyone here. We will definitely take Monero to the Moon! |
|
|
|
Serbian translation done!
Thank You! I waited only for that to push the next release Monero Client v0.26.0https://github.com/Jojatekok/monero-client/releases/tag/v0.26.0This release comes with a handy taskbar icon which should notify you about incoming and outgoing transactions. It also provides a little menu for the key functions. Also, the shutdown function just got a lot more stealth and smooth: exit crashes should not be experienced anymore (but if they do, just send me a report about it ). An important fix is also included for transaction sending with decimal numbers. No bugs are known yet for this version, so happy hunting for everyone! |
|
|
|
I can do a Greek and Afrikaans translation if needed.
Afrikaans would be much appreciated! :O Please visit https://www.transifex.com/organization/jojatekok/dashboard/monero-client I have improved the shutdown experience for the next release (including support for non-safe process killing), along with a nice little feature  EDIT: Oh, and I also fixed transaction sending: it turns out that the problem was environment-related with decimals ('.' was interpreted as ',', and simplewallet didn't like it ) |
|
|
|
was there ever any clarification on when bounty contest ends? July 1st?
Yes, probably. I also requested some clarification about this some posts before. By the way, I just got so passionate about this project that I surely won't cancel its development, even after the bounty ends. It's just lovely to see all the positive feedback I receive, especially as just a high-schooler. I'm indescribably grateful for all the translators who are helping to spread the message of Monero around the world. You guys are awesome, and really deserve a shout-out! |
|
|
|
Monero Client v0.25.0 has been released!https://github.com/Jojatekok/monero-client/releases/tag/v0.25.0It introduces a new feature: localization at runtime (So you don't have to close the program in order to switch between languages anymore.)There are also many core function changes which improve the performance by a lot (just look at the wallet console log printer's responsiveness): Numerous asynchronous operations have been merged into separate threads in order to consume less CPU clocks. More core API-related changes are in the works: stability is enormously important for all of us, isn't it? EDIT #1: I noticed that the application crashes when it's closed. It cannot cause any kind of data loss, but I'll try to resolve it in the next version.EDIT #2: Also, non-passphrase-protected wallets will still ask for a passphrase by a mistake because of preparation for the next update. Please keep using v0.24.0 if you have an unprotected wallet!
|
|
|
|
|
Show Posts
