HaikuDepot exits abnormally

When I run Haikudepot in hrev58719,Bug report said that:

Debug information for team /boot/system/apps/HaikuDepot (3219):
CPU(s): 2x Intel QEMU Virtual version 2.5+
Memory: 2.93 GiB total, 519.25 MiB used
Haiku revision: hrev58719 Mar  9 2025 07:21:54 (x86_64)

Active Threads:
	thread 3219: HaikuDepot (main)
	thread 3226: Package Contents Populator 
	thread 3232: w>Haiku軟體庫 
	thread 3235: team 3219 debug task 
	thread 3234: LocalPkgDataLoadProcess 
		state: Call (double free 0x37c66a7540)

		Frame		IP			Function Name
		-----------------------------------------------
		00000000	0x79007927f7	_kern_debugger + 0x7 
			Disassembly:
				_kern_debugger:
				0x00000079007927f0:   48c7c0eb000000  mov $0xeb, %rax
				0x00000079007927f7:             0f05  syscall <--

		0x7ffb4f9ec9a0	0x790081c877	wrterror + 0xa7 
		0x7ffb4f9eca30	0x790081e0d2	ofree.constprop.0 + 0x772 
		0x7ffb4f9eca80	0x790081f954	free + 0x74 
		0x7ffb4f9ecab0	0x1f7fb158838	BReferenceable::ReleaseReference() + 0x98 
		0x7ffb4f9ecad0	0x391cd0e230	PackageInfo::SetCoreInfo(BReference<PackageCoreInfo>) + 0x20 
		0x7ffb4f9ecf50	0x391cd15ef9	LocalPkgDataLoadProcess::RunInternal() + 0x6f9 
		0x7ffb4f9ed030	0x391cd12652	AbstractProcess::Run() + 0xc2 
		0x7ffb4f9ed070	0x391cd21d1b	ThreadedProcessNode::_RunProcessStart() + 0x5b 
		0x7ffb4f9ed080	0x391cd21ef4	ThreadedProcessNode::_RunProcessThreadEntry(void*) + 0x4 
		0x7ffb4f9ed0a0	0x7900791507	thread_entry + 0x17 
		00000000	0x7f3044ef1258	commpage_thread_exit + 0 

		Registers:
			  rip:	0x00000079007927f9
			  rsp:	0x00007ffb4f9ec4a8
			  rbp:	0x00007ffb4f9ec990
			  rax:	0x00000000000000eb
			  rbx:	0x00000079008301b8
			  rcx:	0x00000079007927f9
			  rdx:	0x00007ffb4f9ebfb9
			  rsi:	0x000000790082d72f
			  rdi:	0x00007ffb4f9ec4d0
			   r8:	0x0000000000000000
			   r9:	0x0000000000000000
			  r10:	0x0000000000000000
			  r11:	0x0000000000000202
			  r12:	0x00007ffb4f9ec4d0
			  r13:	0x00000037c66a7540
			  r14:	0x0000000000000000
			  r15:	0x0000002d36875c60
			   cs:	0x002b
			   ds:	0x0000
			   es:	0x0000
			   fs:	0x0000
			   gs:	0x0000
			   ss:	0x0023
			  st0:	0
			  st1:	0
			  st2:	0
			  st3:	0
			  st4:	0
			  st5:	0
			  st6:	0
			  st7:	0
			  mm0:	{0, 0, 0, 0}
			  mm1:	{0, 0, 0, 0}
			  mm2:	{0, 0, 0, 0}
			  mm3:	{0, 0, 0, 0}
			  mm4:	{0, 0, 0, 0}
			  mm5:	{0, 0, 0, 0}
			  mm6:	{0, 0, 0, 0}
			  mm7:	{0, 0, 0, 0}
			 xmm0:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm1:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm2:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm3:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm4:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm5:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm6:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm7:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm8:	{0, 0, 0, 0, 0, 0, 0, 0}
			 xmm9:	{0, 0, 0, 0, 0, 0, 0, 0}
			xmm10:	{0, 0, 0, 0, 0, 0, 0, 0}
			xmm11:	{0, 0, 0, 0, 0, 0, 0, 0}
			xmm12:	{0, 0, 0, 0, 0, 0, 0, 0}
			xmm13:	{0, 0, 0, 0, 0, 0, 0, 0}
			xmm14:	{0, 0, 0, 0, 0, 0, 0, 0}
			xmm15:	{0, 0, 0, 0, 0, 0, 0, 0}



What did you do when it crashed?
Did you try to search for something while the package list was still loading?

Same thing happened to me. When you enter some text to Search before it loads content - it throws up error

thread 3226: Package Contents Populator

Hello; Could I please ask you to read this post and re-test your problem with that new build.

**

Any manual on how to read these reports? Lets say I wanna look at code and see what value is stored on memory/register/function for debuging in terms of “alright by looking for this func on tthis addres I can go quickly to part XY of code Z and start” :sleepy: :sleeping: or something that is usefull for me as “C++/+Hex” noobie? It would be usefull on how to understand bigger bugs or kernel exception ?.. Wanna dive deep into this part of code exploring

**

Start here and first get a local build working. If you have that sorted out, you can build it with;

DEBUG=1 jam -q HaikuDepot

This will produce a debug build. You can then then launch it with the Debugger tool from the generated directory;

Debugger objects/haiku/x86_64/debug_1/apps/haikudepot/HaikuDepot

It would be good if you can test with that build for me as the problem is most likely fixed in that piece of work.

No,things you mentioned is on the last version. :sweat_smile:

In these version I do nothing and it report bug,even the loading is not finished.

The report is too long to paste here.

Ok,it fixed.

1 Like

Update:With hrev58745,the problem appear again.

Seems to work and exit OK on hrev58752 x64.

1 Like

Please try again with a version on or after hrev58752.

1 Like