(using hrev58477 and latest Iceweasel nightly 128.5.0esr (64-bit))
On some content heavier pages, even like here, e.g.:
IceWeasel goes into a little rendering frenzy and CPU load gets very high.
View updates are stalled and when closing/quitting the app, it takes a while and can even lead to a crash with the memory manager.
Is this a known issue? Couldn’t find anything in the Github issues…
Debug information for team /boot/system/apps/Iceweasel/Iceweasel (858):
CPU(s): 8x Intel 11th Gen Core™ i7-1165G7
Memory: 31,85 GiB total, 4,87 GiB used
Haiku revision: hrev58477 Dec 29 2024 07:15:46 (x86_64)
Active Threads:
thread 858: MainThread (main)
thread 905: IPC I/O Child
thread 921: pool-spawner
thread 922: gmain
thread 929: pool-/boot/syst
thread 965: Socket Thread
thread 968: HTML5 Parser
thread 969: StyleThread#1
thread 970: StyleThread#2
thread 971: StyleThread#3
thread 972: StyleThread#4
thread 973: StyleThread#5
thread 976: JS Watchdog
thread 983: Backgro~Pool #1
thread 1003: Timer
thread 1005: RemVidChild
thread 1018: ImageIO
thread 1019: Worker Launcher
thread 1025: ImageBridgeChld
thread 1026: ProcessHangMon
thread 1115: RemoteLzyStream
thread 1146: pthread func
thread 1147: pthread func
thread 1148: pthread func
thread 1149: pthread func
thread 1150: pthread func
thread 1151: pthread func
thread 1152: pthread func
thread 1153: pthread func
thread 1491: DOM Worker
thread 42335: StreamT~ns #122
thread 42351: team 858 debug task
thread 919: Iceweasel
state: Exception (Invalid opcode exception)
Frame IP Function Name
-----------------------------------------------
0x7ff62b6a66d0 0xc65290f02c js::gc::IncrementalProgress js::gc::GCRuntime::markWeakReferences<js::gc::SweepGroupZonesIter>(js::SliceBudget&) + 0x4c
Disassembly:
js::gc::IncrementalProgress js::gc::GCRuntime::markWeakReferences<js::gc::SweepGroupZonesIter>(js::SliceBudget&):