Crash report fails to send

[petersampsonaudacity]

Bug description

Many times now I have encountered failure to send an Audacity error report, the ET-phone-home dialog, when I click the Send button.

This has worked for me in the past - it is only in recent times that this seems to be happening. A couple of posters on the Forum have also reported similar recently.

Steps to reproduce

1. do something that causes the Crash Report dialog to appear
2. Click Send

Expected behavior

Crash report to be sent to base

Actual behavior

Crash report not sent to base

Audacity Version

current master

Operating system

All OSs

[crsib]

The issue has been reported to our SA team.

[LWinterberg]

Does this still happen?

[crsib]

We still get messages about it

…

On Fri, Feb 24, 2023, 11:37 LWinterberg ***@***.***> wrote: Does this still happen? — Reply to this email directly, view it on GitHub <#4154 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUJSFHLB7BMO7EGBMY77VDWZBXOJANCNFSM6AAAAAATTJWQSE> . You are receiving this because you commented.Message ID: ***@***.***>

[petersampsonaudacity]

Yes it does - I still get it and we get Forum reports of this failure to send

[petersampsonaudacity]

Seems to be working here on my W11 Zürich PC

[petersampsonaudacity]

Seems to be working these days on my Manchester W10 PC

[LWinterberg]

I guess this is done then

[petersampsonaudacity]

@crsib @LWinterberg @chinakov

It's started happening again - consistently when I test the crash on record immediately after launch on the latest alphas:
Windows: Record crashes latest 3.4.0 alphas #4996

[dozzzzer]

Confirm the issue is present again on Windows 11.

[LWinterberg]

I'm getting this right now. Interestingly, posting the stack trace into github doesn't work either because it runs over the character limit. Is sentry perhaps constrained to 2^16 characters for crash reports?

[JohnColket]

Also just reported on forum here: https://forum.audacityteam.org/t/3-4-crash-when-loading-opus-file/88991

[crsib]

This is not an issue with Audacity per se. We will try to do some build with extensive logging and/or proxy support for the crash sender. This way we probably will be able to provide more info for SA.

This issue is not a blocker for 3.4.1, for this reason I remove it from this milestone.

[JohnColket]

Another similar report on Forum today: https://forum.audacityteam.org/t/3-4-crashing-when-trying-to-open-audacity-projects-in-windows-10/89168

[Leogamr]

I am having this a lot. So often that I am having to save backups of backups. And there is PLENTY of space on my machine and no writing/access limitations.

[dozzzzer]

@Leogamr as for the "Audacity Configuration Error" you're having, it may be happening due to the Read-Only permissions of the audacity.cfg file in C:\Users\<user>\AppData\Roaming\audacity. Please make sure that the "Read-only" flag is unchecked in the file's Properties dialog.

[Fydon]

When Audacity is failing to send crash reports, what is the best way to send these? I have a repeatable crash when exporting audio for a particular file

[LWinterberg]

@Fydon if you have a repeatable crash, please create a new bug with steps to reproduce