-
By pressing F5 several times you can notice a non-returning increase in ram usage. The bug occurs in explorer. My Windows is 7 (updated since 2015-2023 - avoiding not using Windows 10).
-
```
When a CALL is made to bad memory, the return address gets pushed onto the
stack, and then the instruction pointer moves to the new bad address and the
crash occurs. Stackwalking from the topmos…
-
```
When a CALL is made to bad memory, the return address gets pushed onto the
stack, and then the instruction pointer moves to the new bad address and the
crash occurs. Stackwalking from the topmos…
-
```
When a CALL is made to bad memory, the return address gets pushed onto the
stack, and then the instruction pointer moves to the new bad address and the
crash occurs. Stackwalking from the topmos…
-
```
When a CALL is made to bad memory, the return address gets pushed onto the
stack, and then the instruction pointer moves to the new bad address and the
crash occurs. Stackwalking from the topmos…
-
```
When a CALL is made to bad memory, the return address gets pushed onto the
stack, and then the instruction pointer moves to the new bad address and the
crash occurs. Stackwalking from the topmos…
-
### Windows Terminal version
1.19.11213.0 & 1.21.1272.0
### Windows build number
Win10 22H2 build 19045.4355
### Other Software
N/A
### Steps to reproduce
Windows Terminal will n…
-
```
Dear Google-Breakpad Team,
I have encountered an issue that I would like to submit:
Procedure:
1. Load a Windows crash dump with WinDBG and acquire the symbols from the
Windows Symbol server:
(S…
-
```
Dear Google-Breakpad Team,
I have encountered an issue that I would like to submit:
Procedure:
1. Load a Windows crash dump with WinDBG and acquire the symbols from the
Windows Symbol server:
(S…
-
```
Dear Google-Breakpad Team,
I have encountered an issue that I would like to submit:
Procedure:
1. Load a Windows crash dump with WinDBG and acquire the symbols from the
Windows Symbol server:
(S…