- In the past weekend i was backtesting a lot. I got a lot "Haasonline Trade Server has stopped working"
From the last 10 crashes i made screenshots from the Windows problem details like "CLR20r3" , "APPCRASH" (kernelbase.dll), "System.OutOfMemoryException" if Stephan needs this.
I see the memory footprint of HTS is high mostly over 1700MB. I think it leaks lots of memory on backtesting/autotuning (30+ times) and then crashes.
Mostly after autosetup/autotune and the values are negative. Because haasbot.com is not caching all alt-coins(it should if you really want to support alt) i have to wait hours to start and building hours of track... (i prefer a week/month of backlog!). maybe add an api to HTS to add my own ticks from my own (tobuild)caching server?
- The profits of Cryptsy are totaly wrong in the tradelog, it shows 10% feecost in the tradelog!?
- A lot of time after a save and restart or a crash i loose all my tradebot settings
- when my trade amount is higher then my wallet (because of losses), it blocks trading and i lose even more money.
- on windows start, i was stuck in the updater. HTS was not running for hours, losing money
- lots of time in the debug i see HTS thinking it had a succesfull trade, after hours i found out and had to correct(change coin position) manually.
- today HTS pages are not parsing and get the #indicator.data fields(now its ok again)
- using the HTS api from my own scripts is resulting in a lot of refreshes/unwanted redirections when i check the website manually the same time
- simulation time should be the time of the moment it was of the simulated trade, now its the time of the simulation action. (i really want to compare it to the real market)
- At the moment i get no Cryptsy tracking at all:
2014-03-03 09:41:27.870 |TRACKER_INFO| Reading of Cryptsy failed, retrying....
2014-03-03 09:41:28.214 |TRACKER_INFO| Reading of Cryptsy failed, retrying again....
2014-03-03 09:41:29.183 |TRACKER_INFO| Reading of Cryptsy failed, next retry on next update.
2014-03-03 09:41:29.198 |ERROR| The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
2014-03-03 09:41:29.292 |DEBUG| System.Net.WebException: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
at System.Net.HttpWebRequest.GetResponse()
at Cryptsy.CryptsyAPI.CryptsyQuery(Boolean authenticate, Dictionary`2 args)
at Cryptsy.CryptsyAPI.GetOpenMarkets(Boolean basicInfoOnly)
at TradeServer.Trackers.API.CryptsyTracker.UpdateTracker()
Am i the only one with this Cryptsy problems?
Stephan, we have wonderfull features now, and if they worked stable they are very valueable. I hope you see its really time to put the next effort in fixing bugs and memory leaks. Also i hope the other customers agree to wait for new features in return for a stable release.
cpusher