Upcoming Event with Twin Oaks Computing

February Newsletter 2014

Welcome to the Twin Oaks Computing, Inc Newsletter!

Our monthly newsletter brings you news and information about Twin Oaks Computing and our CoreDX DDS middleware. Be sure to "like", "follow" and "friend" us on our Social Networking sites for fun facts, free giveaways, and stories about Communications Middleware, Technology, and Twin Oaks Computing.

Twin Oaks Computing and aicas to present “Building Connected M2M Devices using DDS” at EE Live!

Intelligent devices can optimize their operation with more information about their environment by communicating with other intelligent devices. Attendees will learn how to create a peer-to-peer publish/subscribe network using OMG DDS clients with JamaicaVM on Raspberry Pis. All of the attendee's Raspberry Pis will simulate forming an intelligent "mesh" of devices. Click here for more information.

Twin Oaks Computing speaking at the Design Automation Conference

June 5, 2014: Using the standardized Data Distribution System (DDS) technology as an example, this presentation describes the concepts and tools necessary to determine and analyze the resource utilization of middleware components in embedded systems. Register here.

Twin Oaks Computing will Present at AUVSI

May 14, 2014: Save the Date! Twin Oaks Computing will discuss “The Use of DDS Communications Middleware in Autonomous Vehicles and in Space” at a Beyond the Booth Showcase. More information can be found here.

Frequently Asked Question: Memory Leaks

Question:My subscribing CoreDX DDS application has a memory leak somewhere. I’ve trimmed it down to a simplified application using CoreDX DDS, so I’m wondering if it is possible the leak is in CoreDX DDS?

Answer:Of course, anything is possible. However, we regularly and thoroughly test our CoreDX DDS products with an eye on memory, including very detailed profiling of every memory allocation and de-allocation. Let start at some common mistakes that can cause memory leaks in a subscribing CoreDX DDS application.

1. Neglecting to call return_loan() after every successful read() and take() call.
2. Neglecting to clear your data and sample_info sequences in between successive calls to read() or take().
3. Allowing the samples to grow in your DataReader cache (for example, a History.kind = KEEP_ALL with infinite Resource Limits where the samples are not removed using take() or a configured Lifespan).
4. Allowing the instances to grow in your DataReader cache (for example, an infinite ResourceLimits.max_instances where the DataWriter is not properly managing instance lifecycles).

If none of these are applicable in your application, please provide us with some sample code and/or the output from a memory profiling tool (for example, valgrind) and we will provide additional assistance.

Click here to learn more

Upcoming Events

March 24-28, 2014 OMG Technical Meeting, Reston, VA, USA Read more...

March 26-27, 2014 MD&M BioMedDevice, Boston, MA, USA. To meet with a Twin Oaks Computing representative, click here.

April 1, 2014 EE Live!, San Jose, CA, USA. Read more...

April 15-17, 2014 AIA Vision, Boston, MA, USA. Read more...

May 12-15, 2014 AUVSI, Orlando, FL, USA. Read more...

June 1-5, 2014 DAC, San Francisco, USA. Read more...

October 5-9, 2014, 2014 DASC, Colorado Springs, CO, USA. Read more...

October 15-17, 2014 RoboBusiness, Boston, MA, USA Read more...

October 29-30, 2014 MedTechWorld MD&M, Minneapolis, MN, USA Read more...

For more information about Twin Oaks Computing:

"Follow" us on Twitter...

"Like" us on Facebook...

View Twin Oaks Computing on Pinterest...

View Twin Oaks Computing Power Point Presentations discussing everything from Android to Interoperability on Slideshare...