Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If leap is not connected unreal process does not stop #24

Closed
baloo887 opened this issue Nov 7, 2018 · 6 comments
Closed

If leap is not connected unreal process does not stop #24

baloo887 opened this issue Nov 7, 2018 · 6 comments
Labels
addressed waiting release bug Something isn't working

Comments

@baloo887
Copy link

baloo887 commented Nov 7, 2018

Hi guys,
I have a strange behaviour in one of my unreal projects, using this plugin.

The problem is: after the end of the execution, if the leap motion is unplugged (and wasn't plugged before), a "U4game.exe" process is kept alive. This process uses 100~400 MB of memory, and one of these task is added at each execution.

This happens only with a packaged project, on windows 10.

Reading the logs and looking at the plugin code, it seems that the shutdown routine of the project is stopped by the "FLeapWrapper::CloseConnection()" method in the LeapWrapper.cpp class.

Can you please check on this issue or advice on how to manage a project that could not have the leap motion device always connected.

P.S.: here's the last rows of my log file:
[2018.11.06-17.42.39:990][446]LogModuleManager: Shutting down and abandoning module LeapMotion (118) [2018.11.06-17.42.39:990][446]LeapMotionLog: Leap Plugin shutdown. [2018.11.06-17.42.39:990][446]BodyStateLog: Id: 1 [2018.11.06-17.42.39:990][446]LogUObjectArray: Warning: Empty slot [2018.11.06-17.42.39:990][446]BodyStateLog: BodyState::Device Detached: Leap Motion (1)

Thanks

@getnamo getnamo added awaiting replication bug Something isn't working labels Nov 7, 2018
@getnamo
Copy link
Contributor

getnamo commented Nov 8, 2018

This sounds like a bug, will try to get a replication. Likely https://github.com/leapmotion/LeapUnreal/blob/master/Source/LeapMotion/Private/LeapWrapper.cpp#L84 which if a device is never found, may never quit, but it should. I suspect https://github.com/leapmotion/LeapUnreal/blob/master/Source/LeapMotion/Private/LeapWrapper.cpp#L467 loop.

@baloo887
Copy link
Author

Thanks for the hints @getnamo, let me know if you're able to reproduce it.

@getnamo
Copy link
Contributor

getnamo commented Jan 7, 2019

note to self: appears LeapPollConnection never times out in v4

getnamo added a commit that referenced this issue Feb 19, 2019
@getnamo
Copy link
Contributor

getnamo commented Feb 19, 2019

should be fixed in e8a536d, repull master for fix.

Fix is a workaround with a timeout of 3 seconds using waitFor instead of open ended wait.

@baloo887
Copy link
Author

I've tested it today and it's working! Thanks for the fix!

@getnamo
Copy link
Contributor

getnamo commented Apr 5, 2019

Latest release supports fix.

@getnamo getnamo closed this as completed Apr 5, 2019
@getnamo getnamo mentioned this issue Apr 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addressed waiting release bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants