When I try to edit an answer, the site freezes. This post for example: How to get images on HTML site to stay in position relative to background image as it scales across screen sizes?
Has anyone experienced this issue? I have two PCs. On both of them the issue is present, but they are strong, so they shouldn't be the reason.
The Rich text mode has this issue. We can repro the issue by switching from Markdown mode/Markdown with preview mode.
All my plugins are disabled.
The log, which is only visible when I check the "Verbose" in the inspector's console:
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
[Violation] 'setTimeout' handler took <N>ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 161ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 58ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 512ms
createjs.min.js:12 [Violation] 'setTimeout' handler took 218ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 337ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 569ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 2368ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 232ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 53ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 261ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 179ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 97ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 82ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 101ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 90ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 92ms
createjs.min.js:12 [Violation] 'setTimeout' handler took 84ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 111ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 82ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 88ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 110ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 85ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 115ms
stacks-editor.en.js?v=cfec1a9b4d6c:1 [Violation] 'setTimeout' handler took 96ms
My browser is Edge. I just checked, and the browser's version was: 140.0.3485.94 (Official build) (64 bytes), I now updated it to 141.0.3537.57, but the error still happening.
I also checked in Firefox, it was: 141.0.2, and now 143.0.4, but the error is still there....
All extensions disabled.
My operating system is Windows 11 Pro 24H2 with a i7-1065G7 CPU with 8 gigs of RAM. The other PC has an Intel Core Ultra 9 185H, with 32 gigs of RAM.
The error happens right after I click on the Edit "button", then it immediately shows the editor grayed out, and the window is then unresponsive.
It seems to happen with larger answers, like this one: https://stackoverflow.com/a/8331169/2817442. It may be the presence of the code...
Another example: What's the best way to generate a UML diagram from Python source code? this: https://stackoverflow.com/a/7554457/2817442 CAN'T be edited, but https://stackoverflow.com/a/260323/2817442 can be, also, these CAN be edited: https://stackoverflow.com/a/260196/2817442
https://stackoverflow.com/a/260183/2817442
https://stackoverflow.com/a/261844/2817442
https://stackoverflow.com/a/8445401/2817442
https://stackoverflow.com/a/263606/2817442
https://stackoverflow.com/a/260649/2817442
https://stackoverflow.com/a/6606829/2817442
Edit:
My suspicion (that "It may be the presence of the code... ") got reinforcement from @Trajanos:
It only happens when the post contains code-block formatting...
