Be Careful With Registrations

You are here

22 March
0
  0

Be Careful With Registrations

We found a memory development in their application which utilized client occasions for interprocess correspondence. The issue we found was that any client occasions which are enrolled however unhandled by an occasion structure will expand your application's memory use when produced. 

A fundamentally the same as the issue was raised at the 2011 CLA summit that produced CAR 288741 (settled for LabVIEW 2013). This CAR was recorded in light of the fact that unhandled enlisted occasions really reset the timeout in occasion structures. There was a great deal of good dialog over at LAVA with clients estimating approaches to utilize this new component however what I didn't see raised anytime was the way that producing client occasions which are not taken care of in an occasion structure will bring about a memory development in your application notwithstanding resetting the occasion timeout. 

From my understanding, we see this conduct on the grounds that the enlist occasions hub will make a post box for occasions to be placed in but since there is not a case in the occasion structure to deal with this particular occasion, it is never removed from the letter box. This will prompt an expansion in the application's memory each time that occasion is produced. I have backpedaled and forward between this being normal conduct and a bug. At the season of composing this I trust it not out of the ordinary conduct yet there are sure things that are either inconsistencies in LabVIEW or demonstrate my misconception of how LabVIEW occasions function. 

One of these irregularities and a reason this issue can be so hard to find is the way unhandled occasions are shown in the Event Inspector Window. 
The issue I have is that albeit "Some Event" is not dealt with in the occasion structure, it doesn't appear in the rundown of Unhandled Events in Event Queue(s). Curiously, the occasion shows up in the occasion log with the occasion kind of "Client Event (unhandled)" which implies LabVIEW knows the occasion is not taken care of in this specific occurrence but rather still keeps it in the post box. What is confounding, to me in any event, is that despite the fact that nothing appears in the occasion monitor's rundown of unhandled occasions, flushing the occasion line discards these occasions (additionally counteracting memory development).

Latest From Blog

Semiconductor Testing
12 December 2017 | 0 comments

Automated test equipment (ATE) is computer-controlled test and measurement equipment that allows for testing with minimal human interaction. The tested devices are referred to as a device under test (DUT).

[Read more]
SUBSCRIBE TO OUR NEWSLETTER

About

“ReadyDAQ provides a customizable LabVIEW solution which is both time saving and affordable”. 

 

The team – ReadyDAQ has a dedicated team of physicists, electrical engineers, and programmers who work to provide a data acquisition solution for any project in different difficulty levels.

CONTACT INFO

  • Address: Matam - Scientific Industrial park, Building 23      Haifa, Israel
  • Phone: +972 72 250 5555
  • Mail: info@ReadyDAQ.com