Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"DTN feed was the only feed that consistently matched Bloomberg feed for BID/ASK data verification work these past years......DTN feed is a must for my supply & demand based trading using Cumulative Delta" - Comment from Public Forum Post
"Can I get another account from you? I am tired of ******* going down so often" - Comment from George
"Very impressed with the quality of your feed - ******* is a real donkey in comparison." - Comment from A.C. via Email
"I used to have *******, but they are way more money for the same thing. I have had no probs with data from DTN since switching over." - Comment from Public Forum Post
"Its working FABULOUSLY for me!! Holy cow...there has been so much I've been missing lately, and with this feed and Linnsoft software...I'm in the game now." - Comment from Chris R.
"I'm very glad I switched to IQFeed. It's working perfectly with no lag, even during fast market conditions." - Comment from Andy via Email
"I started a trial a few weeks back before the market went wild. DTN.IQ didn’t miss anything and beat my other provider. I decided to stay with you because of the great service through all the volatility." - Comment from Mike
"I just wanted to say how happy I am with your service. I was able to download the API docs last week and I was able to replicate Interactive Brokers historical bar queries and realtime bar queries over the weekend. That was about one of the fastest integrations that I've ever done and it works perfectly!!!!" - Comment from Jason via Email
"And by the way, have to say this. I love the IQFeed software. It's rock solid and it has a really nice API." - Comment from Thomas via RT Chat
"With HUGE volume on AAPL and RIMM for 2 days, everyone in a trading room was whining about freezes, crashes and lag with *******, RealTick, TS and Cyber. InvestorRT with IQFeed was rock solid. I mean SOLID!" - Comment from Public IRC Chat
Home  Search  Register  Login  Blogs Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
Viewing User Profile for: jerry walton
About Contact
Joined: May 3, 2008 02:00 PM
Last Post: May 5, 2008 12:01 PM
Last Visit: May 5, 2008 12:01 PM
Website: hyyp://www.symboliclanguages.com
Location: Chicago
Occupation: Computer Programmer
Interests:
Email: jerry.walton@symboliclanguages.com
AIM:
ICQ:
MSN IM:
Yahoo IM:
Post Statistics
jerry walton has contributed to 3 posts out of 19002 total posts (0.02%) in 3,976 days (0.00 posts per day).

20 Most recent posts:

I got this figured out.

It seems that a program using the NxCoreAPI.dll to process a tape,
will grow in memory usage up to about 45-50 MB and then "top off".

I was stopping the program prior to that point because I was
unsure if there was some responsibility on my part to free the
memory used by the messages.

I figured that since the memory was allocated in the NxCoreAPI.dll
that is was the responsibility of the dll to de-allocate/free the memory.

The documentation makes no mention of responsibility for freeing memory
used by messages or the fact that it will grow to a certain point and then catch up.


I thought about it and since the NxCoreAPI is a DLL,
then it is probably a not a good idea to delete an object (memory)
that was allocated by the DLL.

what I am experiencing is that when running SampleOne.cpp to process a tape
and displaying a simple counter - that the program memory just gorws and grows
until eventually the program crashes because it runs out of memory.

so what is the correct way to handle the freeing of resources?

it there anything to code to fix this problem?


I am running the NxCoreAPI sample program (SampleOne) with Visual C++ 2008 Express Edition.

I have read all the documentation and the sample programs and did NOT find a single delete
statement anywhere?

who is responsible for deleting the messages received in the callback?

int __stdcall nxCoreCallback(const NxCoreSystem* pNxCoreSys, const NxCoreMessage* pNxCoreMsg)

who deletes pNxCoreSys and pNxCoreMsg?
when can these be deleted?


Time: Fri March 22, 2019 9:59 AM CFBB v1.2.0 15 ms.
© AderSoftware 2002-2003