Opened 3 years ago

Closed 3 years ago

#12998 closed bug (not reproducible)

app_server crash

Reported by: humdinger Owned by: axeld
Priority: normal Milestone: Unscheduled
Component: Servers/app_server Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

This is hrev50574.

Had app_server crash, see the syslog snippet below. Next time I'll try to get a core file... (Please, someone add the important keyword from this syslog to the summary of the ticket. I don't know what's significant. Also close the ticket, if the info is too vague to be of help...)

KERN: 808: DEBUGGER: _numAvailable <= _numBlocks
KERN: debug_server: Thread 808 entered the debugger: Debugger call: `_numAvailable <= _numBlocks'
KERN: vm_soft_fault: va 0x1d020000 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x1d020000, ip 0x18998d4, write 1, user 1, thread 0x3e97
KERN: vm_page_fault: thread "w:902:offscreen" (16023) in team "app_server" (673) tried to write address 0x1d020000, ip 0x18998d4 ("app_server_seg0ro" +0x1178d4)
KERN: stack trace, current PC 0x618f4114  commpage_syscall + 0x4:
KERN:   (0x70cf7f20)  0x25ab6cd  __assert_fail + 0x51
KERN:   (0x70cf7f50)  0x2623694  isValid__Q28BPrivate10superblock + 0x60
KERN:   (0x70cf7f80)  0x262198d  malloc__Q28BPrivate10threadHeapUl + 0x199
KERN:   (0x70cf7fe0)  0x26224d6  malloc + 0x17a
KERN:   (0x70cf8010)  0x262327c  realloc + 0x110
KERN:   (0x70cf8040)  0xf83297  _SetSize__7BRegionl + 0x9b
KERN:   (0x70cf8070)  0xf83a70  miRegionOp__Q27BRegion7SupportP7BRegionPC7BRegionT2PFP7BRegionP13clipping_rectP13clipping_rectP13clipping_rectP13clipping_rectii_iPFP7BRegionP13clipping_rectP13clipping_rectii_iT5 + 0x64
KERN:   (0x70cf80c0)  0xf838aa  XIntersectRegion__Q27BRegion7SupportPC7BRegionT1P7BRegion + 0x66
KERN:   (0x70cf8100)  0xf83072  IntersectWith__7BRegionPC7BRegion + 0x32
KERN:   (0x70cf8160)  0x1848295  VisibleContentRegion__6Window + 0x41
KERN:   (0x70cf81a0)  0x1849883  InvalidateView__6WindowP4ViewR7BRegion + 0x22f
KERN:   (0x70cf8268)  0x1838fa1  _DispatchViewMessage__12ServerWindowlRQ28BPrivate12LinkReceiver + 0x3099
KERN:   (0x70cf85a8)  0x1835e16  _DispatchMessage__12ServerWindowlRQ28BPrivate12LinkReceiver + 0x12ce
KERN:   (0x70cf86d8)  0x1840f60  _MessageLooper__12ServerWindow + 0x258
KERN:   (0x70cf8758)  0x181542c  _message_thread__13MessageLooperPv + 0x28
KERN:   (0x70cf8788)  0x25a3383  thread_entry + 0x23
KERN: 761: DEBUGGER: _numAvailable <= _numBlocks
KERN: vm_soft_fault: va 0x75676000 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x75676572, ip 0x185efab, write 0, user 1, thread 0x23b2
KERN: vm_page_fault: thread "a:9135:x-vnd.Ink-Vision" (9138) in team "app_server" (673) tried to read address 0x75676572, ip 0x185efab ("app_server_seg0ro" +0xdcfab)

Change History (3)

comment:1 Changed 3 years ago by jua

Resolution: invalid
Status: newclosed

This is a heap corruption issue, so unfortunately, the backtrace alone is not sufficient to debug it any further. I'll close this ticket, as you said, but if you see it again and can create a core file, please reopen it.

p.s. I think we need another ticket status for cases like this, something like "can't reproduce". Marking it "invalid" doesn't seem quite right here...

comment:2 Changed 3 years ago by humdinger

Resolution: invalid
Status: closedreopened

I've added a status "not reproducible". Let's try it out...

comment:3 Changed 3 years ago by humdinger

Resolution: not reproducible
Status: reopenedclosed
Note: See TracTickets for help on using tickets.