Bug#1043329: gnome-shell crashes with SIGABRT
Jörg Sommer
joerg at jo-so.de
Wed Aug 16 07:55:07 BST 2023
Simon McVittie schrieb am Di 15. Aug, 11:37 (+0100):
> Control: tags -1 + moreinfo unreproducible
>
> On Wed, 09 Aug 2023 at 10:02:00 +0200, Jörg Sommer wrote:
> > #7 0x00007f4c474451ed __libc_message (libc.so.6 + 0x271ed)
> > #8 0x00007f4c474b1a75 malloc_printerr (libc.so.6 + 0x93a75)
> > #9 0x00007f4c474b1c3c munmap_chunk (libc.so.6 + 0x93c3c)
> > #10 0x00007f4c474b61b8 __GI___libc_free (libc.so.6 + 0x981b8)
> > #11 0x00007f4c450e7252 n/a (libmozjs-102.so.0 + 0x8e7252)
> > #12 0x00007f4c450e7c06 n/a (libmozjs-102.so.0 + 0x8e7c06)
> > #13 0x00007f4c44e750e2 n/a (libmozjs-102.so.0 + 0x6750e2)
>
> This looks like memory corruption. Are there any steps you can follow that
> make this crash more likely to happen?
No, I don't know how to reproduce it.
I'm fine when you close this (and the other) report.
> > Maybe the list of my extensions is helpful:
>
> We cannot really support gnome-shell when used with third-party extensions:
> extensions have complete control over the Shell process, and extension bugs
> can easily cause a crash like this.
But an extension written in JavaScript should not be able to cause a
*memory* corruption. That's why it's JavaScript.
I've been using these extensions for months now, but I see these crashes
since two weeks or so. But I know the root cause might be somewhere in a
library, which makes it difficult to track down.
Regards Jörg
--
An SQL query walks into a bar and sees two tables.
He walks up to them and says: "Mind if I join you?"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 269 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20230816/71e809ff/attachment-0001.sig>
More information about the pkg-gnome-maintainers
mailing list