IB TWS - Freezing & Crashing

I am running Windows 10 64-bit with Java(TM) SE Runtime Environment (build 1.8.0_60-b27).
Also running the latest (non-beta) TWS Platform as stand-alone.

I believe the tweak to specify how much memory to use is no longer an option in Java 8 (its supposed to be more dynamic).

I have also re-installed the TWS App and have not noticed a difference. But the problems do seem to occur whenever I want to pull more rows of data. I just tried to do an option roll-over and it ticked over 1GB in memory and just sort of hanged there mocking me :P

So I killed it and re-loaded.

Seems it might be best to re-start it every 1-2 hours now? (A year ago I could leave it running all week without any problems).
 
If you notice any sort of slowness or unresponsiveness, it's probably best to close and restart at a time of your choosing. I find if you open a chart, especially a full screen chart, that seems to leak a little memory. A couple dozen of those throughout the day and it might need a restart. Maybe I should just be switching the ticker and keeping a minimized chart instead of closing it. Having a lot of tickers in your quote monitors probably doesn't help, but in my experience lots of charts tends to be a drag on performance.
 
MoreLeverage said:
If you notice any sort of slowness or unresponsiveness, it's probably best to close and restart at a time of your choosing. I find if you open a chart, especially a full screen chart, that seems to leak a little memory. A couple dozen of those throughout the day and it might need a restart. Maybe I should just be switching the ticker and keeping a minimized chart instead of closing it. Having a lot of tickers in your quote monitors probably doesn't help, but in my experience lots of charts tends to be a drag on performance.
More...

Verrrrrrry interesting.......{thinking thinking thinking....}
I have ~100 or less in underlying, but lots of SPX option strikes/spreads on 3-4 pages (lots == 200-300 lines, total??) and then 2 QuoteMonitor pages of 420 lines each -- So, roughly 100+250+420= easily 800 data lines.
BUT!! I have (roughly) 3-4 graphs "up", and a BookTrader and OptionTrader page. That seems like a minimal load.

All of this (to my reading of your post) would point against issues from data lines, and more towards the graphical end of things.

Just something to add to the mix, I guess.....
 
I'm not sure if options are meaningfully different (don't trade those really), but I have a lot more lines of stocks and stock charts than you and I don't think I noticed anything worse than usual in the recent days. But it's hard to say. Check out some of the threads here on allocating more memory to TWS via the command line invocation, maybe that will help.
 
I have the same problem, have run TWS for several years , never a problem, but in the last several weeks have noticed frequent freezing. It got to where a few weeks ago would have to exit via Task Master about every 2 hours. Did the java updates, reloaded etc. minor relief, but still froze a few times a day.
I found you just have to manage what you got loaded on the TWS and be careful what else you have running on the computer at the same time. Clear off all unused charts and keep the optiontrader off except when needed. These two changes have kept me away from the Freeze ups. The optiontrader seems to hog up memory fast, I notice when it starts to take several seconds to get a chain the end is near, so I finish the trade and turn off the optiontrader completely.
 
I had the same problem. Had to shut down via task manager about every two hours.

Testing around the end of December.

· Latest TWS and Java. Windows 10

· Two machines, both i7s lots of memory etc. One brand new with nothing else installed.

· Both machines with no changes to the installed TWS. Only the default symbols watched. No trading. Nothing, just sitting there running in the freshly installed state.

· In about two hours, freeze and shut down via Task Manager.

Installed previous version, Build 952.3b on both machines, everything works great again.

I'm guessing that the latest TWS has not been tested properly seeing as it has a rather glaring bug for those who auto-trade (at least for me). When a trade is made via the API, the symbol does not automatically show up in the table (it does do the trade and it appears in the account/log).

So for me, the only two things I tested, just running and trading thru the API, both failed. This is no doubt why when IB releases a new version of TWS they leave the older, stable, version available for download.
 
tommcginnis said:
Verrrrrrry interesting.......{thinking thinking thinking....}
I have ~100 or less in underlying, but lots of SPX option strikes/spreads on 3-4 pages (lots == 200-300 lines, total??) and then 2 QuoteMonitor pages of 420 lines each -- So, roughly 100+250+420= easily 800 data lines.
BUT!! I have (roughly) 3-4 graphs "up", and a BookTrader and OptionTrader page. That seems like a minimal load.

All of this (to my reading of your post) would point against issues from data lines, and more towards the graphical end of things.

Just something to add to the mix, I guess.....
More...

I had the freeze ups and cpu/memory hogging observed in Task Manager by running

1) 3 tabs of of daily charts with about 8 instruments each.
2) Option trader with default strikes and tabs

I only use TWS as a chart book and occasionally generate a series of spread combinations which I eventually delete.

I suspect it is the chart data requests. Additionally, requesting data via API seems to have gotten a lot harder.
 
@HappyTrader, I had the same shit for quite a while.

I was running the 32bit standalone version on 64bit windows 10, because up until recently my excel sheet wouldn't run properly with 64bit version.

I removed 32bit (TWS and Java) last week and did a new install of 64 bit versions of both Java and TWS (latest built 963.2b) and works great. I do get those annoying popups saying dll isn't working...

I also changed Java heap size to 2G in tws.vmoptions-file (located somewhere in Jts folder)... although that sometimes changes back to original setting when TWS is updated.

No problems anymore.
 
JackRab - thanks for the details, I will give the Java memory setting a try as I think the command line settings no longer work as of a little while ago for increasing that.

Following up on my post above about charts leaking memory, I often review lots of charts one at a time over the weekend for the coming week's prospects. When I normally opened a new chart for each stock, I would run into the problem TWS became sluggish and eventually unresponsive after a few dozen names. Mind you this is with no market data or trades coming in.

Today I tried my theory that it was the creation and destruction of the chart that imposed a larger memory cost. Instead, I opened one big chart and cycled the symbol through each stock on my list without closing it. I made it through well over a hundred instead of 20-30, although it was getting sluggish at the end there.

In short, one thing that might help if you look at a lot of new charts during the day is to keep a chart open, possibly mimimzed, to use for looking at new situations (rather than the static charts you have open and just watch).
 
You must log in or register to reply here.
Back
Top