| Summary: | Crash on big-endian arches in JSC::VM::VM() | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Gratton <mike> | ||||
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED DUPLICATE | ||||||
| Severity: | Normal | CC: | berto, cgarcia, clopez, dkg, mcatanzaro | ||||
| Priority: | P3 | Keywords: | Gtk | ||||
| Version: | Other | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Attachments: |
|
||||||
|
Description
Michael Gratton
2020-03-16 22:50:22 PDT
From the backtrace it seems that the mprotect() call in JSC::Config::permanentlyFreeze() is failing. I assume that this is WebKitGTK 2.28.0 ? > I assume that this is WebKitGTK 2.28.0 ?
Looks like 2.26 from the build logs. Not sure if Debian has packaged 2.28 yet. It's an issue that has been present for a number of versions though.
Yes, 2.28 is in Debian already (in testing/unstable and also in stable via backports) i'm the person who generated the backtrace. It was on a ppc64 machine (perotto.debian.net), and it was in a context with the debian webkit package 2.28.0-2 installed. If anyone has any suggestions on how to isolate the problem so that there isn't so much geary involved, i'm happy to try to replicate it more narrowly. This is also noted in the debian BTS as https://bugs.debian.org/954026 I understand that this is a duplicate of bug 209236 , correct ? (In reply to Alberto Garcia from comment #5) > I understand that this is a duplicate of bug 209236 , correct ? Yes. *** This bug has been marked as a duplicate of bug 209236 *** Note this crash is related to page size; it has nothing to do with endianness. |