Opened 12 years ago

Closed 12 years ago

#1562 closed bug (fixed)

[registrar] crash

Reported by: diver Owned by: bonefish
Priority: normal Milestone: R1
Component: Servers/registrar Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Trying to reproduce one of my old bugs i stress tested system by running almost all apps in /boot/beos/bin. This time whithout consoled, CortexAddonHost, pack_cis, sync, shutdown and vim) Registrar crashed and i was welcomed by fullscreened gdm complaining that it could not find it's core files, so bt doesn't work.

vm_soft_fault: va 0x1d not covered by area in address space
vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x1d, ip 0x315412, write 0, user 1, thread 0x2a
vm_page_fault: sending team "/boot/beos/system/servers/regis" 0x26 SIGSEGV, ip 0x315412 ("libbe.so_seg0ro" +0xcd412)
stack trace:
  0x0031571c (libbe.so_seg0ro + 0xcd71c)
  0x0031559e (libbe.so_seg0ro + 0xcd59e)
  0x00306583 (libbe.so_seg0ro + 0xbe583)
  0x00307ed5 (libbe.so_seg0ro + 0xbfed5)
  0x00307ac3 (libbe.so_seg0ro + 0xbfac3)
  0x00516ad0 (libroot.so_seg0ro + 0x20ad0)
  0x700c1fec (main_mime_2a_stack + 0x3ffec)
vm_soft_fault: va 0x0 not covered by area in address space
vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x8009b92c, write 0, user 0, thread 0x2a
debug_server: Thread 42 entered the debugger: Segment violation
stack trace, current PC 0x315412  IsFinished__C15RegistrarThread + 0x6:
  (0x700c1e9c)  0x31571c  CleanupThreads__22RegistrarThreadManager + 0x50
  (0x700c1edc)  0x31559e  MessageReceived__22RegistrarThreadManagerP8BMessage + 0x2a
  (0x700c1f0c)  0x306583  DispatchMessage__7BLooperP8BMessageP8BHandler + 0x5b
  (0x700c1f3c)  0x307ed5  task_looper__7BLooper + 0x211
  (0x700c1f7c)  0x307ac3  _task0___7BLooperPv + 0x3f
  (0x700c1fac)  0x516ad0  _get_next_team_info + 0x5c (closest symbol)
38: DEBUGGER: getNumAvailable() == 0

Change History (3)

comment:1 by bonefish, 12 years ago

Should be fixed in hrev22534/hrev22535. At least here all programs start (respectively fail to start) now, although it takes ages and the system is extremely unresponsive part of the time. Please verify.

comment:2 by diver, 12 years ago

Tested twice with hrev22537 and this time registrar no longer crash. I had to increase memory in vmware to be able to start all apps. It took about 5 min to complete and after that system became very unresponsive as you said.

Please close this bug. Thanks!

comment:3 by bonefish, 12 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.