From: "Alex Bennée" <1896298@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1896298] Re: TCG memory leak with FreeDOS 'edit'
Date: Tue, 25 May 2021 14:51:07 -0000 [thread overview]
Message-ID: <162195426790.4432.9270067480094392796.malone@soybean.canonical.com> (raw)
In-Reply-To: 160046874518.13612.4861858859499751315.malonedeb@gac.canonical.com
Just to repeat the work around discussed on the GitLab page: -accel tcg
,tb-size=32 will prevent the rapid increase of memory due to self
modifying code.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1896298
Title:
TCG memory leak with FreeDOS 'edit'
Status in QEMU:
Expired
Bug description:
qemu trunk as of today leaks memory FAST when freedos' edit is
running.
To reproduce, download:
https://www.ibiblio.org/pub/micro/pc-
stuff/freedos/files/repositories/1.3/cdrom.iso
Then run:
$ qemu-system-i386 -cdrom cdrom.iso
select your language then select "return to DOS", then type
> edit
it will consume memory at ~10MB/s
This does NOT happen when adding -enable-kvm
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1896298/+subscriptions
next prev parent reply other threads:[~2021-05-25 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 22:39 [Bug 1896298] [NEW] memory leak Michael Slade
2020-09-18 23:20 ` [Bug 1896298] " Michael Slade
2020-12-02 7:55 ` Thomas Huth
2021-05-11 13:35 ` Thomas Huth
2021-05-13 12:16 ` [Bug 1896298] Re: TCG memory leak with FreeDOS 'edit' Thomas Huth
2021-05-25 14:51 ` Alex Bennée [this message]
2021-05-25 16:45 ` [Bug 1896298] [RFC PATCH] accel/tcg: change default codegen buffer size for i386-softmmu Alex Bennée
2021-05-25 16:45 ` Alex Bennée
2021-06-03 16:33 ` Alex Bennée
2021-06-03 16:33 ` [Bug 1896298] " Alex Bennée
2021-06-03 19:04 ` Richard Henderson
2021-06-04 7:42 ` Alex Bennée
2021-06-04 7:42 ` [Bug 1896298] " Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162195426790.4432.9270067480094392796.malone@soybean.canonical.com \
--to=1896298@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.