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

bug: crash, Subscript used on non-accessible variable when using Groupy software #17

Closed
samkatakouzinos opened this issue May 14, 2020 · 25 comments
Assignees
Labels
bug Something isn't working fixed high-priority High priority

Comments

@samkatakouzinos
Copy link

This occurs by opening and closing Windows Explorer.

WindowTop_WIq2IRbruA

System Info:

OS Name Microsoft Windows 10 Pro
Version 10.0.18363 Build 18363
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ****
System Manufacturer Gigabyte Technology Co., Ltd.
System Model To be filled by O.E.M.
System Type x64-based PC
System SKU To be filled by O.E.M.
Processor Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3901 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. F15, 23/10/2013
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Product B75M-D3H
BaseBoard Version x.x
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.752"
Username SKG-DV-002\samka_urshi1t
Time Zone AUS Eastern Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 4.93 GB
Total Virtual Memory 31.9 GB
Available Virtual Memory 14.0 GB
Page File Space 16.0 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

@gileli121
Copy link
Member

Can you try please to run the program while Windows booted into safe mode and see if it still happens?

I suspect that the issue caused by some other program.
If it will work on safe mode, it will tell that I am right and we continue to debug it from there.

Thanks.

@gileli121 gileli121 self-assigned this Jun 2, 2020
@jakkaas
Copy link

jakkaas commented Jun 10, 2020

Same thing happening with me whlie switching apps using version 3.4.5. Not happening with Version 3.3.10
image
Thanks

@gileli121 gileli121 added the bug Something isn't working label Jun 10, 2020
@gileli121
Copy link
Member

@jakkaas The error message the same as in the original report?
You also see there "Line 5123" ?

@jakkaas
Copy link

jakkaas commented Jun 10, 2020

Yes Same Error
image

@gileli121 gileli121 added the high-priority High priority label Jun 11, 2020
@gileli121
Copy link
Member

Thanks for the report.
I will investigate why it happens and try to solve it.

@gileli121
Copy link
Member

gileli121 commented Jul 3, 2020

I am investigating the issue using the piece of information you all gave that it line 5123 and version 3.4.5.
Seems that you all have Groupy (https://www.stardock.com/products/groupy/) installed, I am right?

There was a fix in v3.3.8 for Groupy software
Fixed: compatibility issue with Groupy software that when the window is maximized, the arrow menu bar does not show
Fixed: compatibility issue with Groupy software with Shrink-Pro mode – when doing un-shrink on a tabbed window, the window loses the tab view
Fixed: compatibility issue with Groupy software with Shrink-Pro mode – when shrinking maximized window in a tab view, Groupy tabs still showing
Fixed: compatibility issue with Groupy software with Shrink-Pro mode – when shrinking & unshrinking window that viewed as tab, the window gets out of the tab list

The strange thing is that one of you said that with v3.3.10 it worked fine.
Maybe I did bad git merge.

I will try to see how v3.4.5 works when Groupy installed

@gileli121
Copy link
Member

Update:
I was right. I was able to reproduce the error with Groupy software.

Steps to reproduce

  1. Groupy must be installed and running
  2. Switch the monitor to another monitor

It does work with one monitor.
But with 2 monitors there are issues.

I will work on a fix for this issue

@gileli121
Copy link
Member

So the steps I wrote were not the right steps.
The steps are:

  1. Groupy must be installed and running
  2. Open some window
  3. Close the window

And indeed, it will work fine with v3.3.10 as users reported here

@gileli121
Copy link
Member

Issue fixed.
I will close the bug when the version with the fix will be released.

@samkatakouzinos
Copy link
Author

Yes I use Groupy.

@gileli121
Copy link
Member

I know. I was only needed to know the line number :)

Please extract this file:
WindowTop.zip

Exit WindowTop if it is running and copy the WindowTop.exe to
C:\Program Files\WindowTop
Delete the original WindowTop.exe and copy the new WindowTop.exe to there.

Please try this version and let me know if it works stable with Groupy

@gileli121
Copy link
Member

Something else got broken in the version I just sent you.
Don't try it yet.

@gileli121 gileli121 changed the title bug: crash, Subscript used on non-accessible variable bug: crash, Subscript used on non-accessible variable when using Groupy software Jul 4, 2020
@gileli121
Copy link
Member

gileli121 commented Jul 4, 2020

WindowTop v3.4.6-test.zip
Please try this file.
Put it instead of the WindowTop.exe file in C:\Program Files\WindowTop

Please let me know how it works for you with Groupy

It includes also fix for bugs #31 , #30 , #29

@samkatakouzinos
Copy link
Author

It goes well so far. No notifications. No silent exits.
Keeping the old version name in the test software threw me a little but no biggie.

@gileli121
Copy link
Member

Great to hear!
I did not understand your last sentence - Keeping the old version name in the test software threw me a little but no biggie.

@samkatakouzinos
Copy link
Author

When I was running the new version and visited 'About WindowTop …' it showed v3.4.5.
Thought it might have had the word 'test' or similar in there.

@gileli121
Copy link
Member

Yes, I did not update the version number in the code.
Ignore it.

When I will release the new version, it will show another version number.

I will close this issue when I will release the new version.

@jakkaas
Copy link

jakkaas commented Jul 5, 2020 via email

@gileli121
Copy link
Member

Thanks @jakkaas for this report!
This is a big issue and it happens also in v3.4.5
I opened issue #32

@gileli121
Copy link
Member

@jakkaas
Please try this file and let me know if fixed for you.
WindowTop - fix2.zip

@jakkaas
Copy link

jakkaas commented Jul 5, 2020 via email

@gileli121
Copy link
Member

Released in v3.4.6

@gileli121
Copy link
Member

Reopened.
This bug is back in v5 that rewritten in C#

@gileli121
Copy link
Member

Fixed in v5 (Not released yet)

@gileli121
Copy link
Member

Released in v5.1.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed high-priority High priority
Projects
None yet
Development

No branches or pull requests

3 participants