[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of vir
From: |
Yang Yingchao |
Subject: |
bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory |
Date: |
Mon, 15 Apr 2024 09:36:50 +0800 |
User-agent: |
mu4e 1.12.3; emacs 29.3.50 |
-------------------- Start of forwarded message --------------------
From: Yang Yingchao <yang.yingchao@qq.com>
To: Eli Zaretskii <eliz@gnu.org>
Subject: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory
Date: Mon, 15 Apr 2024 09:21:04 +0800
Hi * Eli*,
On Sun, Apr 14 2024, Eli Zaretskii wrote:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: bjorn.bidar@thaodan.de, yang.yingchao@qq.com, 70352@debbugs.gnu.org
>> Date: Sun, 14 Apr 2024 14:28:33 +0800
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > I thought the question I asked was for you to answer, not for the OP:
>> > how come the OP bumped into a problem that (AFAIU) could only happen
>> > when using code that is not in the Emacs Git repository?
>>
>> Because the OP, presumably, built code that I published elsewhere (and,
>> I had hoped, discreetly enough to avoid the attention of casual Emacs
>> users).
>
> If that's what happened, then yes, it explains everything (and means
> we don't need to discuss this issue anymore).
Sorry for the late response.
And actually, I was wrong about the GTK version. I mistook the GTK version as
the GTK+ version...
Here is the actual version related to GTK+:
```
$ ldd emacs | grep gtk
libgtk-3.so.0 => /usr/lib64/libgtk-3.so.0 (0x00007f1e4ba00000)
```
If any other information is required, please let me know.
Regards,
-- *Yang Yingchao*
-------------------- End of forwarded message --------------------
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Yang Yingchao, 2024/04/12
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Po Lu, 2024/04/12
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Eli Zaretskii, 2024/04/13
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Po Lu, 2024/04/13
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Eli Zaretskii, 2024/04/13
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Björn Bidar, 2024/04/13
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Po Lu, 2024/04/13
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Eli Zaretskii, 2024/04/14
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Po Lu, 2024/04/14
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Eli Zaretskii, 2024/04/14
- Message not available
- Message not available
- bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory,
Yang Yingchao <=
- Message not available
- Message not available
- bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Yang Yingchao, 2024/04/14
- Message not available
- Message not available
- Message not available
- bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Yang Yingchao, 2024/04/17
- bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Eli Zaretskii, 2024/04/27
- bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Yang Yingchao, 2024/04/29
- bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Po Lu, 2024/04/29
- bug#70352: Fwd: Re: bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Yang Yingchao, 2024/04/29
- bug#70352: 29.3.50; emacs-pgtk: possible leak of virtual memory, Björn Bidar, 2024/04/13