Yes, I did [create that] but it seems like it’s too destructive and causing [the] system [to become] unusable.
I don’t mean to kick up sand, but, that sounds like normal Haiku software. Haiku is only second to ReactOS as the most unstable OS I’ve ever used (sadly I’ve never gotten to try Copland OS.) Isn’t the web browser still causing kernel panics when you try to use it?
Isn’t the web browser still causing kernel panics when you try to use it?
I only know of one intermittently-reproducible kernel panic from the web browser, and it’s mostly on an issue on recently nightly builds only, not beta5 (it’s due to recently-added assert failing). What crashes are you encountering? We have Haiku VMs that accumulate pretty long uptimes for package builds with no crashes…
I didn’t know either of them were particularly unstable, although I’m less surprised about ReactOS. I think they started that in the slightly-wrong direction of duplicating the NT architecture with new code rather than just API-compatible services atop a proven core, and will forever be stuck in a bad place because of it.
I don’t mean to kick up sand, but, that sounds like normal Haiku software. Haiku is only second to ReactOS as the most unstable OS I’ve ever used (sadly I’ve never gotten to try Copland OS.) Isn’t the web browser still causing kernel panics when you try to use it?
I only know of one intermittently-reproducible kernel panic from the web browser, and it’s mostly on an issue on recently nightly builds only, not beta5 (it’s due to recently-added assert failing). What crashes are you encountering? We have Haiku VMs that accumulate pretty long uptimes for package builds with no crashes…
I didn’t know either of them were particularly unstable, although I’m less surprised about ReactOS. I think they started that in the slightly-wrong direction of duplicating the NT architecture with new code rather than just API-compatible services atop a proven core, and will forever be stuck in a bad place because of it.