Opened 6 years ago

Closed 6 years ago

#9820 closed bug (fixed)

Deskbar crash on shutdown/reboot

Reported by: Giova84 Owned by: axeld
Priority: normal Milestone: R1
Component: Applications/Deskbar Version: R1/Development
Keywords: deskbar crash on shutdown and reboot Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

hrev45736

When i reboot or shutdown Haiku, Deskbar, most of times, will crash. Unfortunately, since Deskbar seems the last component which is closed (also after input_server) i cannot click on "save report" and also, after a reboot, i don't see any message related to Deskbar inside the syslog. In anyway this is reproducible if i quit Deskbar from a Terminal window using:

hey Deskbar quit

After this command, in the syslog i can read these messages:

KERN: vm_soft_fault: va 0x0 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x2161e8b, write 0, user 1, thread 0xa8
KERN: vm_page_fault: thread "Deskbar" (168) in team "Deskbar" (168) tried to read address 0x0, ip 0x2161e8b ("runtime_loader_seg0ro" +0xde8b)
KERN: debug_server: Thread 168 entered the debugger: Segment violation
KERN: stack trace, current PC 0x2161e8b  topological_sort__FP7image_tUlPP7image_tUl + 0x4f:
KERN:   (0x631b3ac0)  0x2162c30  get_sorted_image_list__FP7image_tPPP7image_tUl + 0xb4
KERN:   (0x631b3af0)  0x215ed9c  terminate_program + 0x28
KERN:   (0x631b3b20)  0xf19640  exit + 0x38
KERN:   (0x631b3b50)  0x861ff8  _start + 0x64
KERN:   (0x631b3b90)  0x21635ae  runtime_loader + 0x132
KERN: debug_server: Killing team 168 (/boot/system/Deskbar)
KERN: debug_server: TeamDebugHandler::Init(): Failed to get info for team 168: Operation on invalid team
KERN: debug_server: KillTeam(): Error getting info for team 168: Operation on invalid team
KERN: debug_server: Killing team 168 ()

Change History (14)

comment:1 by diver, 6 years ago

Looks like a dupe of #6803. What replicants do you have in your Deskbar? Also registrar shouldn't offer to save report (or anything?) if input_server is not running.

comment:2 by Giova84, 6 years ago

I have many replicants: ProcessController, Deskcalc, Vacuum IM, WebVideoPlayer, and some script file inserted using desklink. In anyway the crash dialog appear on the monitor for few istant (Terminate, Debug, Save report) but i cannot click on them, since mouse pointer is inactive due no longer running input_server.

comment:3 by diver, 6 years ago

Could you spot which replicant is causing this crash?

comment:4 by Giova84, 6 years ago

Sure. That is my test:

1 i have removed all replicants from Deskbar. 2 i have added one replicant at once 3 after adding replicants (one at once), everytime i have tried to quit again the Deskbar using "hey Deskbar quit" 4 Deskbar will never crash. 5 I have rebooted Haiku and this time Deskbar don't crash. 6 Rebooted again, all is still ok.

Is very odd, because is about one month that i have noticed this (and i also have waited to open this ticket about, to be sure of the issue).

Seems that the fact to have "cleaned" the Deskbar from all replicants, has acted, in some way, as fix about this crash. But the replicants, currently, are all the same as one hour ago.

If i will encounter again this issue i will post again in this ticket.

comment:5 by Giova84, 6 years ago

After several hours of usage i rebooted Haiku again. Deskbar has crashed again. This issue seems more related to hours of usage, instead of a replicant which cause the issue (?)

comment:6 by anevilyak, 6 years ago

That still points to a replicant issue. Bear in mind all of them run in Deskbar's address space, and as a consequence any of them having a bug that causes a crash will cause Deskbar itself to.

comment:7 by Giova84, 6 years ago

hrev45938 This bug seems no longer present (i've updated Haiku just now: i have added many replicants to Deskbar and for now, after reboot/shutdown, no longer crash). Maybe was related to http://dev.haiku-os.org/ticket/9860 ?

comment:8 by Giova84, 6 years ago

Nothing to do: after some hours of use, Deskbar still crash again on reboot/shutdown. As i've said previously https://dev.haiku-os.org/ticket/9820#comment:4 i've done some tests but without success. Some suggestion?

On older revisions (at least before of hrev45736) this doesn't occurs.

comment:9 by diver, 6 years ago

Please attach your syslog after such a crash.

comment:10 by Giova84, 6 years ago

This is what syslog exactly shows when i reboot Haiku and when the Deskbar crash. I also posted this in the first post:

KERN: bfs: bfs_open_dir:1615: Not a directory
KERN: vm_soft_fault: va 0x0 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x1ef3e8b, write 0, user 1, thread 0x1d8
KERN: vm_page_fault: thread "Deskbar" (472) in team "Deskbar" (472) tried to read address 0x0, ip 0x1ef3e8b ("runtime_loader_seg0ro" +0xde8b)
KERN: debug_server: Thread 472 entered the debugger: Segment violation
KERN: hda_stream_stop()
Last message repeated 1 time
KERN: remove_memory_type_range(6664, 0xfe7f4000, 0x4000, 0)
KERN: set MTRRs to:
KERN:   mtrr:  0: base: 0xb7d90000, size:    0x10000, type: 0
KERN:   mtrr:  1: base: 0xb7da0000, size:    0x20000, type: 0
KERN:   mtrr:  2: base: 0xe0000000, size: 0x20000000, type: 0
KERN:   mtrr:  3: base: 0xc0000000, size: 0x40000000, type: 1
KERN: stack trace, current PC 0x1ef3e8b  topological_sort__FP7image_tUlPP7image_tUl + 0x4f:
KERN:   (0x616062a0)  0x1ef4c30  get_sorted_image_list__FP7image_tPPP7image_tUl + 0xb4
KERN:   (0x616062d0)  0x1ef0d9c  terminate_program + 0x28
KERN:   (0x61606300)  0xcb9640  exit + 0x38
KERN:   (0x61606330)  0xb6e028  _start + 0x64
KERN:   (0x61606370)  0x1ef55ae  runtime_loader + 0x132
KERN: Mouse device exiting, Interrupted system call

comment:11 by Giova84, 6 years ago

I have some more info. Currently, in the Deskbar i just have the clock and only two replicants: process controller and a simple text file added using "desklink". If i run Haiku for about 40 mins, Deskbar doesn't crash on shutdown/reboot. If i run Haiku for than more an hour, then, Deskbar will crash on shutdown/reboot.

hrev45938

comment:12 by Giova84, 6 years ago

Ok: after some days of deep investigation seems that i have found the culprit:

"Beam_DeskbarItem" which is a component of the "Beam" mail client. I have never seen a Beam replicant in the Deskbar since i use Beam ( by various months, so, the "Beam_DeskbarItem" seems useless). But seems that since DEP was activated in Haiku, this component cause a Deskbar crash. I have deleted "Beam_DeskbarItem" and i no longer experience Deskbar crashs!

For now i suggest to leave this ticket open, to see if some other replicants may cause Deskbar crashes.

comment:13 by Giova84, 6 years ago

I have reinstalled BeAM on Haiku PM (about two weeks ago), and his deskbar replicant works properly (before has never worked for me). And in anyway there are no replicants which cause Deskbar crashes again.

This ticket can be closed.

comment:14 by diver, 6 years ago

Resolution: fixed
Status: newclosed

Thanks for the feedback!

Note: See TracTickets for help on using tickets.