trader.say and cpu usage issue in 1.41.00

[Apzeltukas]

Hello,
Windows 10 64bit
Since 1.41.00 64bit update i have 3 issues:

1. trader.say() does not speak any more.
   At first i got some strange windows error which I traced to missing "C:\Windows\System32\Speech_OneCore\common\SpeechRuntime.exe" file. Windows file system check and update got it fixed, no more errors, but still trader does not speak.
2. Hitbtc only - works fine while script is running but not yet trading. normal memory usage is below 200MB and cpu like 5%. but if script start to trade, then cpu usage issue and possible memory issue happens. had to kill process today with not responding due to cpu core usage and 600+MB of memory usage.
3. Hitbtc only - "my transactions" are loaded correctly on startup, but does not refresh on live trading

update1 text to be more clear and issue nr3 added
update2 point nr2. turns out there is no issue with repeated orders. it seemed that way due to point nr3.

[JulyIghor]

Can you please confirm, is 2 and 3 fixed in latest release?

[Apzeltukas]

I will try out and report back.

In the meantime, it got false flagged by Avast at first updater and later trader itself

[JulyIghor]

In the meantime, it got tagged by Avast at first about update and later trader itself

Thanks, I'll report the false detection to Avast

ditekshen/detection#12

[Apzeltukas]

number 2 not fixed. additional info. if program is left on screen, after 24h program is not responding due to large memory/cpu usage. but if program is hidden to tray, after 24h memory and cpu usage is not affected. will test some other exchanges next for the same issue.

number 3 not fixed. still the same. loads, but not updates.

[Apzeltukas]

Number 2 is the same for Poloniex and Binance exchanges. Memory use increase if trader is left open on screen. Memory does not increase if trader is hidden to tray.

[JulyIghor]

Number 2 is the same for Poloniex and Binance exchanges. Memory use increase if trader is left open on screen. Memory does not increase if trader is hidden to tray.

It is possible that you have a loop in your script code, we can't inspect it without the code itself.
But for sure you may try to inspect it by yourself, and add to the log output your trade attempts.
Most likely you will see a infinite open order commands that may cause the memory issue.

[Apzeltukas]

It is possible that you have a loop in your script code, we can't inspect it without the code itself. But for sure you may try to inspect it by yourself, and add to the log output your trade attempts. Most likely you will see a infinite open order commands that may cause the memory issue.

No. Without any scripts running, just sitting open fullscreen for like 4 days, Poloniex grew to 1900mb of memory.
While other instances hidden in the tray with scripts running did not increased their memory use.
Can I help in any way?

[JulyIghor]

No. Without any scripts running, just sitting open fullscreen for like 4 days, Poloniex grew to 1900mb of memory.

Maybe you had opened a Debug window?

[Apzeltukas]

Maybe you had opened a Debug window?

No. Do not use a debug window, it is always closed. Unless it is somehow active while closed since Enabled is selected when i open it.
So far i use trader minimized to tray. No significant memory growth for weeks while in tray. That is the only difference i can tell.

[JulyIghor]

No. Do not use a debug window, it is always closed. Unless it is somehow active while closed since Enabled is selected when i open it. So far i use trader minimized to tray. No significant memory growth for weeks while in tray. That is the only difference i can tell.

Thanks, we have reproduced it, but not found a reason for that yet. We will fix it in a future update.