-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trader.say and cpu usage issue in 1.41.00 #282
Comments
Can you please confirm, is 2 and 3 fixed in latest release? |
I will try out and report back. In the meantime, it got false flagged by Avast at first updater and later trader itself |
Thanks, I'll report the false detection to Avast |
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. |
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. |
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? |
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. |
Thanks, we have reproduced it, but not found a reason for that yet. We will fix it in a future update. |
Hello,
Windows 10 64bit
Since 1.41.00 64bit update i have 3 issues:
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.
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.
The text was updated successfully, but these errors were encountered: