Bugzilla – Bug 1776
Side by Side errors
Last modified: 2020-12-28 09:44:32 UTC
Audacity shows "Side by Side" errors in Application Event Log. I've no idea how important this is, hence no idea what priority it should be given.
Additional information in this mailing list thread: https://sourceforge.net/p/audacity/mailman/message/36104946/
J Henric wrote: (Audacity-devel, 7th Nov 2017) > I played around a bit with this and I think, > https://github.com/henricj/audacity/commit/8b1ae0226c7c149af7045e12581ff7c11229ed85 > should do it for the "let's just handle the manifest > ourselves" option. It's for my x64 branch, so it has a few > extra "<GenerateManifest>false</GenerateManifest>" lines, > but it should be simple enough to adapt to master. So it looks as if we have a fix and it just needs to be applied.
Henric offered a fix. The fix was in a branch with many other changes before it, and unfortunately it did not cherry-pick easily out of that branch. I did the work of figuring out just the minimal changes to base onto master, shortly before 2.2.1, but decided this was not priority. Now I addressed that loose end and pushed to master. We have time to verify this for 2.2.2. I ask others on the team to verify it. https://github.com/audacity/audacity/commit/0c88c8de88eeefa7522641e836874dffaeaa7b33
Created attachment 755 [details] Event Viewwr showing details of Side by Side error
Testing on W10 with latest alphas I am still seeing occasional Side by Side errors in the Event viewer. It appears to be consistently Event 78 See attached screenshot. I have tried running the alpha with even viewer open to try to see what might provoke this - but with no success. This does not appear to hinder or impact Audacity. Accordingly I'm reopening this bug
Re Comment 5. I just had a look at this. I discovered that OLD versions of Audacity (and DarkAudacity) can cause this error to be reported EVEN IF THERE WAS NO ATTEMPT TO RUN THEM. Looking at your screenshot, lowest pane, Audacity 2.2.1 is causing the first SxS 78 error, not Audacity 2.3.0. I believe that 2.3.0 is actually already free of this error. However, having read the first comment on https://forums.adobe.com/thread/2222149 I pushed a further change that insists on 32 bit common controls which should be 'even safer'. https://github.com/audacity/audacity/commit/c2e07b4620026439ce71a8fc9adb7f8cd786628d I confirmed this still runs fine on my 64 bit system. ---- I presume that Windows periodically checks configurations of program files, perhaps as part of virus checking, even when it is not running the programs and that is why you see errors in the log for old versions. So back to DEVEL FIX-MADE, and if your log shows all-clear for 2.3.0 itself, I think this can be closed.
(In reply to James Crook from comment #6) Testing and discussions with James on W10 seems to confirm James' suppositions in comment#6 The versions that appear to be affected are 2.1.3, 2.2.0, 2.2.1 and Dark Audacity. I only ever see Side by Side 78 errors listed for these for releases usually grouped/clustered. Sometimes thes erroos will show in the event viewer when running other versions of Audacity - and sometimes they will occur with no other versions of Audacity running at all. In addition to 2.2.2 and 2.3.0 alpha I also have on my machine a reasonably full set of Audacity versions all the way back to 0.8 - and I so no SBS 78s for these. I am now experimenting by removing 2.1.3, 2.2.0, 2.2.1 and Dark Audacity from my PC (temporarily moved off onto a USB stick). If I continue to see no more SBS 78 errors I shall close this bug as it does not seem to be affecting 2.2.2 and 2.3.0. Paul indicated in Comment #2 that this was likely to be fixed for 2.2.2 - but no-one tested it (I had no idea how to, until a little research undertaken recently) I have already been running 2.2.2 and 2.3.0 after that - and thus far no errors - but I plan to let the C sit quietly without Audacity running overnight (lasdt night I got a couple of clusters. I do anticipate that when I restore 2.1.3, 2.2.0, 2.2.1 and Dark Audacity to my PC that once again I will get SBS78s for those versions reported. But that will not stop us closing off this bug as it appears not to affect either the current release 2.2.2 or the upcoming 2.3.0.
(In reply to Peter Sampson from comment #7) Sorry Paul's comment was Comment #3
So with 2.1.3, 2.2.0, 2.2.1 and Dark Audacity i experienced no overnight SNS 78 error reports - nor this morning when running 2.2.2 and 2.3.0 alpha. Accordingly I shall close this bug as RESOLVED
Reopening as there has been a new report of this bug with Audacity 2.3.2: https://forum.audacityteam.org/viewtopic.php?p=373862#p373862
(In reply to Steve Daulton from comment #10) There appears to be some doubt as to whether the report in comment #10 was actually an Audacity problem (possibly a plug-in problem). I'm not aware of any other reports of this issue since mid 2019, so closing as fixed.
