The newly announced refresh loop is not a bug and should not be reported as such, the app is actually expected to refresh the page after the renderer crash as a way to recover from it (which is useful when renderer doesn't crash constantly or at least much better that letting WebCord to display grey window instead).Įlectron Forge going crazy once CI were publishing v4.4.2 distributables. Given v4.4.1 has implemented the safe mode that should help with renderer crashes caused by issues specific to given GPU, I assume it's not a problem due to GPU. There's still no fix (or viable workaround) for regression since v4.4.0. This release was also forced by Electron/Chromium vulnerability, as in case of v4.4.1. Also see electron/forge#3371 for upstream issue. I've also tried to investigate what change could break it and right now I'm clueless (runner seems to be the same as in runs that succeed, downgrading Node to the previous working version was not enough for it to install appdmg by itself and re-running CI on older commits, even with the lockfile and build config that worked before, also causes a build failure in macOS…). Add an URL to icon in Squirrel makers, which will be added to the registry during installation.Ĭurrently the macOS builds are failing in CI (at DMG creation step), so there are no builds for it either until this will be fixed in some way.Use a better compression in produced RPM packages, most likely improving the resulting size in compassion of previous builds.Display a number of mentions in the tray tooltip, if there are any.Improve the implementation of tray icon changing, so it relies now on Discord's title rather than favicon which seems to be more stable and could optimize the performance a bit (since there's no longer a need to cache, convert and hash favicons).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |