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)




"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.
"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
"If you want customer service that answers the phone, your best bet is IQFeed. I cannot stop praising them or their technical support. They are always there for you, and they are quick. I have used ****** too but the best value is IQFeed." - Comment from Public Forum
"Boy, probably spent a thousand hours trying to get ******* API to work right. And now two hours to have something running with IQFeed. Hmmm, guess I was pretty stupid to fight rather than switch all this time. And have gotten more customer service from you guys already than total from them… in five years." - Comment from Jim
"Interactive Brokers tick data was inconsistent, so I have switched to using DTN exclusively. It is great to no longer have to worry about my datafeed all day long." - Comment from Philippe
"I am enjoying the feed very much - so superior to the broker provided feed I was previously using." - Comment from George
"Awesome response, as usual. It is a sincere and refreshing pleasure to do business with DTN, compared to your competition." - Comment from Ryan
"This is an excellent value, the system is generous (allowing for 500 stocks) and stable (and really is tick-by-tick), and the support is fantastic." - Comment from Shirin via Email
"I have to tell you though that using the IQFeed API is about the easiest and cleanest I have seen for some time." - Comment from Jim
"Very impressed with the quality of your feed - ******* is a real donkey in comparison." - Comment from A.C. via Email
Home  Search  Register  Login  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 20822 total posts (0.01%) in 5,388 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: Wed February 1, 2023 12:38 AM CFBB v1.2.0 16 ms.
© AderSoftware 2002-2003