Re: Memory leak

To: Debian Users <debian-user@lists.debian.org>
Subject: Re: Memory leak
From: Charles Curley <charlescurley@charlescurley.com>
Date: Fri, 11 Feb 2022 15:31:33 -0700
Message-id: <[🔎] 20220211153133.2710b11a@hawk.localdomain>
In-reply-to: <[🔎] 20220211150039.a267abec275cbeb29d7e07fc@gmail.com>
References: <[🔎] 20220211110601.1a5a07d8c9f7713a02fb8e00@gmail.com> <[🔎] 20220211095317.44c2e4da@jhegaala.localdomain> <[🔎] 20220211120159.11355c3a7108d65a74f9b314@gmail.com> <[🔎] 20220211114015.7b6ce33f@jhegaala.localdomain> <[🔎] 20220211150039.a267abec275cbeb29d7e07fc@gmail.com>

On Fri, 11 Feb 2022 15:00:39 -0500
Celejar <celejar@gmail.com> wrote:

> There are several reasons I'm not ready to do that:

Fine, get another browser.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Reply to:

References:
- Memory leak
  - From: Celejar <celejar@gmail.com>
- Re: Memory leak
  - From: Charles Curley <charlescurley@charlescurley.com>
- Re: Memory leak
  - From: Celejar <celejar@gmail.com>
- Re: Memory leak
  - From: Charles Curley <charlescurley@charlescurley.com>
- Re: Memory leak
  - From: Celejar <celejar@gmail.com>

Prev by Date: Installation on a Lenovo IdeaPad Yoga 13
Next by Date: Re: Installing bullseye into previously existing encrypted disk with buster
Previous by thread: Re: Memory leak
Next by thread: Re: Memory leak
Index(es):
- Date
- Thread