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

7.16.16 when doing BOINC Manager Close Window, how does one open BOINC Manager again? #4072

Closed
Ageless93 opened this issue Oct 28, 2020 · 14 comments · Fixed by #4075
Closed

Comments

@Ageless93
Copy link
Contributor

I did File->Close Window. It closes this BOINC Manager window, but does not exit BOINC Manager. It doesn't put BM's icon in the system tray either. Clicking on the shortcut to BOINC Manager on my desktop doesn't (re)open BM either. So how does one reopen this closed window?

A video link showing the problem

@AenBleidd AenBleidd self-assigned this Oct 28, 2020
@AenBleidd
Copy link
Member

Looks like boinctray.exe failed to run. I'll take a look at this, thanks

@Ageless93
Copy link
Contributor Author

???
boinctray.exe is running (it still is even at this moment). It's directly underneath boincmgr.exe in the task manager window in the video. And besides, what should it do then, according to you? It's the idle detection program. It doesn't do anything else (it certainly doesn't put the BM icon in the system tray).

@AenBleidd
Copy link
Member

AenBleidd commented Oct 28, 2020 via email

@RichardHaselgrove
Copy link
Contributor

The Notification Area ("system tray") icon comes from boincmgr itself, not from boinctray (which runs without UI).

I've had multiple problems down the years persuading different releases of Windows 10 to display - and display permanently, not just with notifications - the icons from different releases of BOINC. I'll look tomorrow.

@Ageless93
Copy link
Contributor Author

Ah, I hadn't tested yet what pressing the red X did in the top right corner. Well, same thing. Closes BOINC Manager, and can't be opened again.

Now I do wonder if the size of BOINC Manager increase of 2.5MB matters here.

@AenBleidd
Copy link
Member

No, it doesn't matter. This release was built with the latest wxWidgets, so looks like it should be investigated and fixed

@RichardHaselgrove
Copy link
Contributor

Tomorrow's test will involve running Dependency Walker over it, to see exactly what DLLs are still needed and which can be removed.

And I'll be doing the test (initially at least) on Windows 7, to check for compatibility issues.

@AenBleidd
Copy link
Member

Ok, I have this issue too. Will track it down and fix next days

@RichardHaselgrove
Copy link
Contributor

Further testing - not dependency walker yet, but the more pressing problem of the missing icon.

Windows 7 - the system tray icon displays and operates normally.

Windows 10 (specifically, Windows 10 pro 2004, build 19041.572) - the icon is completely inoperative.

7 16 16 icon small
Once the Manager is minimised, I can find no way of restoring it except by crashing the task via Task Manager.

And of course the autostart at login starts the Manager minimised...

I'd call that a big regression.

@AenBleidd
Copy link
Member

AenBleidd commented Oct 29, 2020 via email

@RichardHaselgrove
Copy link
Contributor

More to the point, WHY IS THIS EXPERIMENT BEING PERFORMED IN THE V7.16 RELEASE BRANCH?

We still have bugs to fix - see #4071. That bug was introduced on 13 May 2020, and should have been disqualified from inclusion in v7.16. We still haven't worked out how people who were caught by it can be rescued.

We spent a long time working out how to use the combined strengths of GitHub and CI testing to best effect. Now, a mixture of arrogant disdain and sloppy planning is putting all that work in jeopardy.

Please - all - re-read https://github.com/BOINC/boinc-policy/blob/master/Development_Documents/Client_Release_Process.md AND FOLLOW IT.

@AenBleidd
Copy link
Member

AenBleidd commented Oct 29, 2020 via email

@RichardHaselgrove
Copy link
Contributor

OK - Dependency Walker test. DW finds these problems:

image
but I think they're all delay-load warnings, and non-critical. Both the client and the manager seem to be running normally on this Win 7 machine. They are all found in both components, and derive from IEFRAME.DLL, either directly or via MSHTML.DLL

More to the point, there are NO remaining dependencies on any third-party DLLs, so the static build has worked. We can remove from the installer

18/12/2016  16:46           362,496 libcurl.dll
25/12/2019  21:46         2,287,616 libeay32.dll
20/02/2011  01:51           608,080 msvcp100.dll
19/02/2011  03:52           829,264 msvcr100.dll
25/12/2019  21:46           386,560 ssleay32.dll
17/10/2013  16:48           106,496 zlib1.dll
           6 File(s)      4,580,512 bytes

That's a lot less than the growth seen in the installer.

@AenBleidd
Copy link
Member

Issue is localized and fixed. PR will be ready soon.

AenBleidd added a commit to AenBleidd/boinc that referenced this issue Oct 29, 2020
This issue affects only Windows 8.1/10 x64 built with VS2013 and VS2019.
The reason is a different memory addressing on these OSs in pure 64-bit mode.

This fixes BOINC#4072.

Signed-off-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants