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)




"Version 4.0.0.2 has been working well for me and I appreciate that it is now a much tighter client to work with. I feel I can go to press with my own application and rely on a stable platform" - Comment from David in IA.
"If someone needs the best quality data and backfill beyond what their broker provides at a rate that is the best in the industry, I highly recommend IQFeed." - Comment from Josh via Public Forum
"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
"I would just like to say that IQFeed version 4 is running very well and I am very happy with its performance. I would also like to extend a big thanks for the fast and efficient help that I always receive. My questions and concerns are always addressed promptly. Way to go!" - Comment from Josh in CO.
"I "bracket trade" all major news releases and I have not found one lag or glitch with DTN.IQ feed. I am very comfortable with their feed under all typical news conditions (Fed releases, employment numbers, etc)." - Comment from Public Forum
"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
"It’s so nice to be working with real professionals!" - Comment from Len
"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
"I am very happy I changed. I love the product, but more so I am thrilled with Tech Support. You are knowledgeable, polite, pleasant and professional." - Comment from Pat
"Can I get another account from you? I am tired of ******* going down so often" - Comment from George
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 21185 total posts (0.01%) in 5,837 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: Thu April 25, 2024 11:01 AM CFBB v1.2.0 10 ms.
© AderSoftware 2002-2003