Control: severity -1 minor
Control: tags -1 + unreproducible
The issue was due to faulty RAM. No further action required.
On Wed, Mar 29, 2023 at 05:01:00PM +0200, karogyoker999 wrote:
> For the others watching (if any): I have sent the core dump to Berto.
The stack trace, for reference:
Core was generated by `/usr/lib/i386-linux-gnu/webkit2gtk-4.1/WebKitWebProcess
12 18'.
Program terminated with signal SIGSEGV, Se
For the others watching (if any): I have sent the core dump to Berto.
On Wed, Mar 29, 2023 at 02:33:14PM +0200, karogyoker999 wrote:
> Yes, it is still crashing by running it that way.
Do you think you would be able to obtain a core dump from one of those
crashes?
Berto
Yes, it is still crashing by running it that way.
Alberto Garcia ezt írta (időpont: 2023. márc. 29.,
Sze, 12:58):
>
> On Wed, Mar 29, 2023 at 06:22:25AM -0400, Karo Gyoker wrote:
>
> > If I try to open any page in epiphany-browser, nothing happens. The CPU is
> > at 100%.
> > I can see it in dme
On Wed, Mar 29, 2023 at 06:22:25AM -0400, Karo Gyoker wrote:
> If I try to open any page in epiphany-browser, nothing happens. The CPU is at
> 100%.
> I can see it in dmesg that WebKitWebProcess is constantly segfaulting.
>
> cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
Package: libwebkit2gtk-4.1-0
Version: 2.40.0-3
Severity: important
X-Debbugs-Cc: karogyoker2+deb...@gmail.com
Dear Maintainer,
If I try to open any page in epiphany-browser, nothing happens. The CPU is at
100%.
I can see it in dmesg that WebKitWebProcess is constantly segfaulting.
[14886.202609
8 matches
Mail list logo