Jump to content

Thanatica

Member
  • Posts

    9
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Everything posted by Thanatica

  1. See: https://muut.com/startisback#!/general:startisback-crashes-only-at I just wanna know what the status of fixing this is please, since the MUUT forum is now completely broken. Thanks.
  2. Here's what to do: Have at least 2 virtual desktops, and 2 monitors Have the taskbar display only the active windows for each desktop, AND only the active windows for each monitor So with 2 monitors and 2 vdesktops, to be extra super clear, have 8 programs spread among them: Virtual desktop 1 Monitor 1 Program A Program B Monitor 2 Program C Program D Virtual desktop 2 Monitor 1 Program E Program F Monitor 2 Program G Program H With that out of the way, let's reproduce the bug: Change the order of taskbar buttons on any of the 4 taskbars, by just dragging them. Go to the other vdesktop. I do this using a 4-finger gesture on my touchpad. Go back to the previous vdesktop. Actual result: Taskbar button order is reset to whatever is was before reordering them manually. It doesn't matter which programs those buttons belong to. It doesn't matter on which monitor you reorder taskbar buttons. It doesn't seem to matter on which vdesktop you do this. Expected result: Taskbar button order is persisted after switching vdesktops. SIB++ 2.9.11 Windows 10 20H2
  3. Here's one: Source Windows Explorer Summary Stopped responding and was closed Date ‎28-‎04-‎2021 09:51 Status Report sent Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Windows\explorer.exe Problem signature Problem Event Name: AppHangB1 Application Name: explorer.exe Application Version: 10.0.19041.928 Application Timestamp: bc61eb13 Hang Signature: f410 Hang Type: 134217728 OS Version: 10.0.19042.2.0.0.256.48 Locale ID: 2057 Additional Hang Signature 1: f41059ebfeab8429f3b790afec2e77a6 Additional Hang Signature 2: f428 Additional Hang Signature 3: f4283016ddebc49996cb4cf3be60a191 Additional Hang Signature 4: f410 Additional Hang Signature 5: f41059ebfeab8429f3b790afec2e77a6 Additional Hang Signature 6: f428 Additional Hang Signature 7: f4283016ddebc49996cb4cf3be60a191 Extra information about the problem Bucket ID: 570a794a6725abc3718d06b4e58fbabd (1264674444376259261) The link you shared shows the same information again, which I already said doesn't generate any crashdumps.
  4. I tried to follow that article, and created `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\explorer.exe` without any further settings. The defaults are fine with me. However, a crash dump is not being stored in `%LOCALAPPDATA%\CrashDumps` after a crash. It might be presumptious of me to add explorer.exe, but I don't know what other process it would be. I don't know what do to next. Can you provide more details on how to get Windows to make a crashdump for SIB++? Also, btw, in order to make it crash, of course I had a more difficult time to make it crash. Just frantically clicking the start buttons did it. At the time of posting this issue, a crash after clicking the secondary start button was pretty much 100% reproducible on my pc. But that was in the afternoon. Maybe in the morning it's different somehow. I don't know what to make of that, but maybe you do.
  5. Thanatica

    Crashes

    SIB++ has been crashing ever since I installed it years ago, but only ever when I click the start button on the secondary screen which is positioned above my primary screen. I've had different kinds of monitors, all positioned above the primary monitor. My primary monitor has always been 4K @ 250%, but my secondary monitor has been a ultrawide @ 125%, a 1440p monitor @150% and now a 4K monitor @200%. So the type of monitor doesn't cause it to crash. I've also gone through several major Windows 10 updates, all the way from the RTM release to the 20H2 update. So the exact Windows version also doesn't matter. I think I've reported this issue before. But it's really starting to kind of irritate me. SIB++ has gone through so many updates and it still crashes... And when it does, it takes down the whole explorer.exe process, costing me a couple of seconds to wait for that to respawn, which is especially irritating when I only wanted to reach the shutdown button. Can this problem please be solved with some kind priority?
  6. This is still happening on two 4K screens with different zoom factors. One is at 250%, and the other at 200%. On the latter one, context menus are bigger - only for SIB++. As for other native explorer context menus (e.g. rightclicking the taskbar), they look normal.
  7. This is still happening, almost daily, sometimes multiple times a day. Crash reports are not generated, the folder for them remains empty. When this happens, I need to keep clicking the start button about 10 times until the process is killed and respawned. During this, both task bars disappear. During this it is impossible to, for example, shut down the computer, even by pressing Alt+F4 on the desktop. It forces me to wait for the crash to recover until I can do what I actually wanted to do - shutdown, so I have to wait for a killed process to be respawned, only to kill it again as part of a shutdown. Ironic, isn't it. Also after a crash, the Night Light feature is reset to normal mode, were this to happen during Night Light hours. That's basically the most irritating about this, as it's a very vibrant visual change on both monitors. It somehow more oftenly seems to crash during these hours (but also during daylight hours!).
  8. I'm using a laptop with 4K screen. I have two external monitors attached. When I click the start button on my built-in 4K screen, the start menu opens just fine. When I click the start button on one of my external monitors, explorer.exe oftenly crashes. This is not 100% reproducible, and doesn't seem to only happen when clicking the start button. It may also happen when hitting the start button on my keyboard with an active window on the external monitors (causing the start menu to display there). As for settings: I have a start button on each monitor, taskbar is locked, not auto hidden, small buttons enabled, peek disabled, buttons never combined, window buttons only appear on the monitor they're on. I'm on virtual desktop 1 (of 2 total). The start button then looks to be unresponsive for a few seconds, so I guess it freezes, and afterwards explorer.exe crashes and respawns itself. Very annoying when trying to get some work done, if I'm totally honest. I'm on Windows 10 x64 (10.0.17134.407) with StartIsBack++ 2.7.2.
  9. I'm using a laptop with 4K screen. I have two LDPI external monitors attached. The start menu on the laptop screen looks fine, but on the external monitor, it is totally blown out of proportions. The context menu is gigantic, and doesn't even fit on screen. Some icons are blown up, while the rest stays normal, making it look "broken". Please compare the attached screenshots. One is on my "normal" LDPI monitor, and the other is on my built-in HDPI screen. Also note that the number of displayed items is different, which is weird. I promise I didn't change any settings (or did anything, really!) in between making these screenshots. Also note that when I'm using *only* a normal LDPI screen, the start menu looks fine. No problems there. This is StartIsBack++ 2.7.2 on Windows 10 (10.0.17134.407).
×
×
  • Create New...