IB rewrote a lot of this code.
BEfore it was clunky but for the most part worked.
Now they rewrote the code AND added new features.
(or just glommed on a bunch of code, or both)
Now it seems broken. Memory loss bug is the worst and overloads Java. The infamous 25% CPU usage across 2 cores; Java VM thrashes becauee the Heap (max VM) is exceeded, even at 1024Mb, the max. Occurs in both 64 and 32 bit java.
Hitting other chart bugs too.
IB if you are monitoring, please fix bugs in charts. IB Testers, testing charts is a target rich environment! Look for refresh events too, status bar updates etc. I bet there are several mem leaks, i.e. no garbage collection.
The irony, is that IB charts were pretty good. They were getting better and better. If the current functionality gets debugged, the Charts in IB will be very good or better.
I usually wait to upgrade and figuered 914.8 would be working, but seems buggy.
What is your opinion? Have they gotten Better or Worse since build 911?
Buggier or Better?
===========
BEfore it was clunky but for the most part worked.
Now they rewrote the code AND added new features.
(or just glommed on a bunch of code, or both)
Now it seems broken. Memory loss bug is the worst and overloads Java. The infamous 25% CPU usage across 2 cores; Java VM thrashes becauee the Heap (max VM) is exceeded, even at 1024Mb, the max. Occurs in both 64 and 32 bit java.
Hitting other chart bugs too.
IB if you are monitoring, please fix bugs in charts. IB Testers, testing charts is a target rich environment! Look for refresh events too, status bar updates etc. I bet there are several mem leaks, i.e. no garbage collection.
The irony, is that IB charts were pretty good. They were getting better and better. If the current functionality gets debugged, the Charts in IB will be very good or better.
I usually wait to upgrade and figuered 914.8 would be working, but seems buggy.
What is your opinion? Have they gotten Better or Worse since build 911?
Buggier or Better?
===========