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

MemGator messages do not appear in Windows UI #290

Closed
machawk1 opened this issue Dec 19, 2017 · 7 comments
Closed

MemGator messages do not appear in Windows UI #290

machawk1 opened this issue Dec 19, 2017 · 7 comments

Comments

@machawk1
Copy link
Owner

Forever fetching:
virtualbox_win10_18_12_2017_19_15_45

Oddly, after installing, if running the script from source with the installation in-place in C:\wail, MemGator does resolve and populate the label (albeit, with overflow):

virtualbox_win10_18_12_2017_19_16_02

@machawk1
Copy link
Owner Author

machawk1 commented Jan 6, 2018

7a2be2b should fix the issue but on my Windows 10 test VM, the "Fetching" message is never replaced when running with the .exe but behaves correctly when running from the .py directly. This issue did not exist prior to the change in 7a2be2b.

This issue persists after a VM reboot using the same .exe.

@machawk1
Copy link
Owner Author

Re-pulled and fetching is removed. Overflow remains. Changing ticket title to address this.

@machawk1 machawk1 changed the title MemGator messages do not appear in Windows UI MemGator messages overflow in Windows UI Jan 22, 2018
machawk1 added a commit that referenced this issue Jan 22, 2018
@machawk1
Copy link
Owner Author

machawk1 commented Jan 22, 2018

Issue only occurs when running from the .exe. A command line UI pops up but disappears too quickly to observe the output, which is likely the memgator call. Observing what this message states might be the means to resolve this issue.

Reverting Issue title

@machawk1 machawk1 changed the title MemGator messages overflow in Windows UI MemGator messages do not appear in Windows UI Jan 23, 2018
@machawk1
Copy link
Owner Author

Likely an issue with subprocess.Popen on Windows per https://github.com/pyinstaller/pyinstaller/wiki/Recipe-subprocess

@machawk1
Copy link
Owner Author

machawk1 commented Feb 2, 2019

Still an issue in the Windows build as of d01e1ae. The "Fetching memento count..." message is never replaced when running the WAIL.exe binary. When running python bundledApps\WAIL.py, the message updates as expected.

@machawk1
Copy link
Owner Author

machawk1 commented Feb 2, 2019

With the --windowed flag removed from the pyinstaller command in MAKEFILE.sh, the resulting binary has the count text updated. Another data point, but this might help narrow down the issue.

@machawk1
Copy link
Owner Author

machawk1 commented Feb 2, 2019

Adding stdin=subprocess.PIPE, stderr=subprocess.PIPE parameters to the Popen command to MemGator causes the text to update from within the .exe binary but causes a window to open each time. Consult the above link for advice on remedying this.

EDIT: This may be mitigating the documented but hidden OSError exception: "[Error 6] the handle is invalid. per the link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant