Iceweasel: Unofficial Firefox port on HaikuDepot

It doesn’t, but not for the reason you expect. It wouldn’t work because the space isn’t escaped, but assuming it was, it would work, it just wouldn’t do what you expect.
For example ls README.{txt,\ md} expands to ls README.txt README.\ md.

1 Like

Iceweasel is getting better with every update! With the latest Wayland-fix as of today (on Haiku nightly hrev58346) I have not experienced a single crash so far.

However, the CPU spikes every other minute and I see a huge load on the gleaner-dispatcher thread (and all idle threads are at 99%). Is this a known issue?
(I’ve only got 5 tabs open or so).

5 Likes

9 posts were split to a new topic: Iceweasel: Telemetry acceptible for Firefox trademarks?

Dear KENZ!
Please move browser cache to the directory /boot/home/config/cache/mozilla/firefox

I don’t think it is easy moving cache folder only from Firefox profile directory. What wrong with you current cache path?

1 Like

Firefox use both AppData/Local and AppData/Roaming on Windows. AppData/Localconfig/cache, AppData/Roamingconfig/setting on Haiku.

3 Likes

screenshot309

@ X512 Thanks for follow-up. I got some idea on it.

@kim1963 I know my build doesn’t put cache there. I asked you what problem occur on you.

I guess some Haiku/BeOS app cleaned there automatically in some condition.

1 Like

Separate placement of cache and settings makes the work of the FilWip application easier.

2 Likes

Thank you for detail!

I’ll work on that in

3 Likes

iceweasel_bin-128.5.0-6

New build will be available. It has a couple of small improvements:

  • Go back/forward with ctrl-arrow left/right key
    • This is streamlined with Haiku native browsers now.
  • You can start autoscroll by clicking middle mouse button.
12 Likes

33 posts were split to a new topic: Iceweasel: This icon, or that icon, or

I don’t see this in HaikuDepot. Is this 64-bit only? Or does it show up in the nightly builds only?

I think it’s 64 bits only due to RAM limitations for the build process.
Cross compiling the 32 bits version may still be possible in theory.

1 Like

If a site uses a font not present in the system, Iceweasel substitutes a different font regardless of its properties. For example, www.ghisler.com is rendered with a Courier-like monospace font, even if the original font is proportional. Is it possible to fix this?

1 Like

I think it is GTK bug as it also happens to GNOME Web.

I guess this is same cause with

2 Likes

(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&):
2 Likes

I’m now using mainly Iceweasel for my daily usage on R1 Beta5 with my NUC Intel (create Haiku Insider articles, browsing internet, youtube, …).

I have to admit it’s quite responsive (better than all others I would say, including WebPositive) and except a few crashes sometimes, it’s really a great port.
I switch back to WebPositive or Falkon only in certain situations :slight_smile:

So a great thank you to have make this port possible to Haiku :clap: :clap: :clap: :1st_place_medal:

11 Likes

Is Haiku R1 Beta 5 fully compatible with an Intel NUC?

Very much depends on the NUC. I have one which works quite well; excepting for there being no Bluetooth support on anything yet.

I suspect some will have the HDA driver pin mapping issues; and there could be other problems too.