Comments (10)
@NeilChien Please try with v1.0.0.4 pre-release and let us know if this issue exists. We recently fixed some bugs.
from grpc-labview.
Hi @ni-sujain thanks for the update.
I will go and check with the v1.0.0.4 version whether have this issue. And will keep updating once I get progress.
from grpc-labview.
Hi @ni-sujain,
I believe the necessary thing I have to do is only to install the 1.0.0.4 version right?
Unfortunately, the opened file amount still increase after I updated gRPC version to 1.0.0.4 version. The problem still there.
Neil
from grpc-labview.
Sorry, I forgot to replace the .so within RT, I am going to have another try.
from grpc-labview.
Hi @ni-sujain
I confirmed that 1.0.0.4 version still exists this issue even if I replace the .so within RT.
Here are the steps :
- Update to 1.0.0.4
- Replace the .so within RT
- Open the project and resolve the broken VIs with "Relink to SubVI".
- Run the Test
from grpc-labview.
@NeilChien
When we do Create Client, some anon_inode:[eventpoll] and anon_inode:[eventfd] files are created and when we do Client Unary Call some sockets are created. On doing Start Server also some similar files are created. The files created during client create and unary call are cleaned up when we call Client Destroy. Similarly, when we do Stop Server the files created during Start Server are destroyed.
If Client Destroy happens first then the client related files are destroyed first and the server files are destroyed afterwards when Server Stop runs. When there is no delay between Destroy Client and Stop Server, sometimes the Destroy Client happens after the Stop Server. In this case some of the files are not cleaned up properly. These files add up over subsequent Server starts and stops.
One way to ensure that Client Destroy happens before Stop Server would be to pass the error out of Destroy Client to Stop Server. In this case there will be no leakage even if there is no delay in between Server Destroy and Stop Server-
from grpc-labview.
Hi @dchakrab-NI,
So, how do we ensure this if the client comes from another where?
You know, in the typical use case, the gRPC client would be created from other systems.
Or do we have a method to check the exist connect from clients?
Neil
from grpc-labview.
Ruhao Gao spoke to Debarka Chakrabarti today. The conclusion is although the test project can reproduce the file leakage issue, it is not a recommended way to coding like this. In our ADAS real use case, it is not exactly the same as the test project. In the meanwhile, based on the recent tests, we don't see the leakages in our real cases any more.
Thus, I don't think we need any fixes and we will keep testing next week to see if everything is good. If no further leakage is found next week, you can close the bug.
from grpc-labview.
Ruhao confirmed that there are no further file leakages, @NeilChien can you please close this bug?
from grpc-labview.
Thank you for all the support.
from grpc-labview.
Related Issues (20)
- grpc-labview client call hangs even though the server responded. HOT 5
- Document java lines in helloworld.proto HOT 2
- gRPC Server halted by invalid Enum received from Client HOT 4
- Calling gRPC Client VIs from TestStand hang at "Wait for Occurrence" while using LabVIEW RTE HOT 11
- Enums in grpc-labview don't support the "=" or ";" characters
- RictToFlat* & FlatToRich* scripted VIs drop unused unbundle & bundle when operating on cluster of "void"
- Urgent: Memory is full HOT 1
- Unable to create new object. HOT 1
- Neighboring Oneof structures issue
- Windows DLL Path HOT 2
- VI Hangs when multiple client reading stream VIs are waiting and multiple Steam Ends occur. This used to work in 1.0.0.1. HOT 5
- Regenerating .proto results in error (since v.1.0.0.6) HOT 6
- Repeated messages with protobuf id >= 16 are packed incorrectly HOT 3
- Wait On Occurrence Wrapper.vi should be re-entrant. Currently causes hang in our app HOT 3
- Labview crashes when two (or more) servers are stopped HOT 6
- grpc-labview currently depends on grpc 1.44, which has high severity CVEs.
- Strange DLL mix=up
- Wait On Occurance Wrapper.vi throws error 8 when labview_grpc_server.dll is deployed in Program Files
- LabVIEW Crashes when Stopping Two Parallel Running gRPC Servers (on Windows and on NI Linux RT) HOT 2
- Handling gRPC exceptions by gRPC Labview HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from grpc-labview.