#6673: [registrar] can be crashed by running multiple instances of mimeset
--------------------------------+----------------------------
Reporter: samui | Owner: bonefish
Type: bug | Status: new
Priority: critical | Milestone: R1
Component: Servers/registrar | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking: 11063
Platform: All |
--------------------------------+----------------------------
Comment (by CodeforEvolution):
As of hrev54154+119 on a x86_gcc2 Haiku system, I can't reproduce the
registrar crash anymore after stress testing the registrar with up to 30
instances of
"for i in `seq 1 100000`; do mimeset -apps -f /system/apps/*; done"
running concurrently.
The only error I notice comes after 8-10 instances of mimeset running
concurrently, in which case the Terminal will start printing "mimeset: no
more threads", which is less troubling than a crash. After closing the
Terminal (which automatically kills all mimeset jobs), everything
continues to work as expected: Apps launch, mimetyping works, and no
errors are even reported to the syslog. I can even try the stress test
again!
Could someone double check on a newer version of the x86_64 version of
Haiku? If all is well, I think this commit a while back may have fixed
what was going on: https://git.haiku-
os.org/haiku/commit/?id=462bfeede0cd123afe2e79d465876289e925ca53
--
Ticket URL: <https://dev.haiku-os.org/ticket/6673#comment:19>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
