You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Interactive Brokers TWS Bug Thread
- Thread starter Kensho
- Start date
Quote from Daal:
Then why the recommended settings are 4GB+ RAM?
You need space for Win7 runtime (especially 64 bit), your API client plus automated trading system, and any other apps you also might be running (browser, email client etc); note that previous poster regulus was also running Multicharts 64.
The sweet spot is 8Gb RAM (in this config you might want to turn off os pagination for better performance) with Core i7 CPU and SSD or hybrid drive.
---The sweet spot is 8Gb RAM (in this config you might want to turn off os pagination for better performance) with Core i7 CPU and SSD or hybrid drive.---
nice...the evolution of TWS. decade ago it was small and will run on any PC. now the sweet spot is a setup that will cost you at least 1K.
nice...the evolution of TWS. decade ago it was small and will run on any PC. now the sweet spot is a setup that will cost you at least 1K.
Quote from atticus:
No weekly options on browser-based, and of course still no risknav on download.
I see both weekly options (for e.g. AAPL) and risknav on 938 build, which is latest browser based; please report your issue to our customer support (e.g. via ticket in account management), thank you.
Quote from dst:
You need space for Win7 runtime (especially 64 bit), your API client plus automated trading system, and any other apps you also might be running (browser, email client etc); note that previous poster regulus was also running Multicharts 64.
The sweet spot is 8Gb RAM (in this config you might want to turn off os pagination for better performance) with Core i7 CPU and SSD or hybrid drive.
You must be mistaken about the CPU. I have a core i3 3rd gen and it is barely used through the day. The avg usage is surely bellow 30% and it rarely spikes much
Quote from dst:
I don't have similar reports plus, you cannot have TWS consume more than 1Gb (it is configured not to go over it)
Dennis,
In order to work around the issue, I changed the 768M default setting for Java maximum heap size to 5G via the Xmx command in the shortcut target field. With this setting, javaw.exe can reach several GB but then will eventually crash. There are no any other processes related to javaw.exe, since when I close TWS, the javaw.exe process will disappear.
I can reproduce this behavior with all TWS versions > 932.4 and with both Java 32 and 64 Bit. Every time I downgraded from the then latest version to 932.4, the issue disppeared completely. With TWS <= 932.4 and more than 80 Charts of tick data in MultiCharts64, I have just around 400 MB of memory consumption after several days of continuous operation.
Quote from regulus:
Since I upgraded from TWS 932.4 to the latest standalone version (938.1), I noticed a significant increase of memory consumption. I run TWS as an API for Multicharts 64 on a Windows 7 64 Bit workstation. With around 50 charts of IB tick data open in MC 64, memory consumption is constantly increasing during operation. After some hours of operation, memory usage reaches several GB until TWS does not react to inputs any more.
Thank you very much for working with us to troubleshoot this issue; it was addressed in just posted TWS beta 9401o, and would soon go out as part of 939 latest build. Would you please try beta and confirm it is working as expected, once we know that we can backport the fix to older builds (e.g. 936).
Quote from dst:
Thank you very much for working with us to troubleshoot this issue; it was addressed in just posted TWS beta 9401o, and would soon go out as part of 939 latest build. Would you please try beta and confirm it is working as expected, once we know that we can backport the fix to older builds (e.g. 936).
This is very good news indeed. I did some time testing with browser based TWS beta 940.1p and Multicharts64. The memory leak issue seems to be resolved, as javaw.exe size stays around 300 MB for hours. I hope the standalone version will show the same behavior with this fix ported to them. Thanks for your support.
Hi all,
This is my first post here. I'm not very familiar with TWS having only used Interactive Brokers for few months.
The issue I have right now is that I can't seem to be able to type any ticker symbols into either my watchlist or into the search bar at the top of the user interface.
I thought I might be on a 'Read only' access mode however I was able to make trades just not able to type in any new securities.
Cheers and sincere apologies if I've been using the wrong terminology. Have been trying to figure out if I accidentally clicked on something. All information is appreciated.
This is my first post here. I'm not very familiar with TWS having only used Interactive Brokers for few months.
The issue I have right now is that I can't seem to be able to type any ticker symbols into either my watchlist or into the search bar at the top of the user interface.
I thought I might be on a 'Read only' access mode however I was able to make trades just not able to type in any new securities.
Cheers and sincere apologies if I've been using the wrong terminology. Have been trying to figure out if I accidentally clicked on something. All information is appreciated.