Ticket #1392 (closed bug: fixed)

Opened 17 months ago

Last modified 11 months ago

[Terminal] app_server could freeze on tab creation

Reported by: diver Owned by: jackburton
Priority: normal Milestone: R1
Component: Applications/Terminal Version: R1 development
Cc: axeld, stippi Blocked By:
Platform: All Blocking:

Description

app_server could freeze on tab creation in Terminal using alt+t For this you have to hit alt+t 10-15 times. After 20 seconds app_server will be back, but terminal will be hopelessly frozen.

Change History

Changed 17 months ago by diver

Oh and another issue, after killing Terminal using Vulcan Death Grip method, Terminal's window will stay on screen. Should i open another bug for this?

Changed 17 months ago by diver

And another one, replicants (e.g. ProcessController) don't react on mouse events anymore after app_server wakeup.

Changed 17 months ago by diver

  • cc axeld, stippi added

I'm even managed to crash terminal this way.

vm_soft_fault: va 0x2000 not covered by area in address space
vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x2000, ip 0x7df79d, write 1, user 1, thread 0x146
vm_page_fault: sending team "/boot/beos/apps/Terminal" 0x13e SIGSEGV, ip 0x7df79d ("libroot.so_seg0ro" +0x2979d)
stack trace:
  0x007dfd65 (libroot.so_seg0ro + 0x29d65)
  0x007e0867 (libroot.so_seg0ro + 0x2a867)
  0x007e0ce1 (libroot.so_seg0ro + 0x2ace1)
  0x00219843 (Terminal_seg0ro + 0x19843)
  0x0021c25c (Terminal_seg0ro + 0x1c25c)
  0x0021bda2 (Terminal_seg0ro + 0x1bda2)
  0x00225ffd (Terminal_seg0ro + 0x25ffd)
  0x00225be5 (Terminal_seg0ro + 0x25be5)
  0x00224156 (Terminal_seg0ro + 0x24156)
  0x002f7f0f (libbe.so_seg0ro + 0xc2f0f)
  0x003a2889 (libbe.so_seg0ro + 0x16d889)
  0x003a5d80 (libbe.so_seg0ro + 0x170d80)
  0x002f944f (libbe.so_seg0ro + 0xc444f)
  0x007d67d0 (libroot.so_seg0ro + 0x207d0)
  0x70102fec (Terminal 1_146_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 0x800959b8, write 0, user 0, thread 0x146
debug_server: Thread 326 entered the debugger: Segment violation
stack trace, current PC 0x7df79d  __Q28BPrivate10superblockiiPQ28BPrivate9hoardHeap + 0x21:
  (0x7010293c)  0x7dfd65  makeSuperblock__Q28BPrivate10superblockiPQ28BPrivate11processHeap + 0x2f9
  (0x7010296c)  0x7e0867  malloc__Q28BPrivate10threadHeapUl + 0xabf
  (0x701029bc)  0x7e0ce1  calloc + 0x149
  (0x701029ec)  0x219843  __10TermBufferiii + 0xd7
  (0x70102a1c)  0x21c25c  _InitObject__8TermViewPCc + 0x74
  (0x70102a6c)  0x21bda2  __8TermViewiiPCcl + 0x276
  (0x70102aac)  0x225ffd  __14CustomTermViewllPCcl + 0x31
  (0x70102aec)  0x225be5  _AddTab__10TermWindowPCc + 0x165
  (0x70102bcc)  0x224156  MessageReceived__10TermWindowP8BMessage + 0x2da
  (0x70102d9c)  0x2f7f0f  DispatchMessage__7BLooperP8BMessageP8BHandler + 0x5b
  (0x70102dcc)  0x3a2889  DispatchMessage__7BWindowP8BMessageP8BHandler + 0x1391
  (0x70102f1c)  0x3a5d80  task_looper__7BWindow + 0x270      

I found this test case very useful to find all sorts of bad thing (zombie deskbar, empty task in team monitor, unkillable windows, shifted context menus, focus lost, etc, etc).

Changed 17 months ago by jackburton

  • status changed from new to assigned

Looks like memory is exhausted, and Terminal doesn't handle this gracefully. I'll look into it.

Changed 11 months ago by jackburton

Although I limited the number of tabs to 6 (for various reasons, including the fact that too many tabs were just unhandy) in r23700, I couldn't freeze the app_server anymore. Terminal, though, did freeze, more or less when the memory were close to be exhausted. Shall I close this bug, and eventually open a new one for the terminal problem ?

Changed 11 months ago by axeld

  • status changed from assigned to closed
  • resolution set to fixed

Yes please.

Note: See TracTickets for help on using tickets.