Opened 3 years ago

Closed 3 years ago

#11399 closed defect (fixed)

[CL2]Press enter many times in write activity and system will hang up.

Reported by: garysu Owned by: jnettlet
Priority: high Milestone: 1.75-software
Component: x window system Version: 1.75-C1
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: test in build
Verified: no

Description

Image:os883.zd8
OFW:Q4C03
Procedure:
1.Enter to sugar.
2.Open write activity
3.Press Enter several times until next page then write will hang-up and system no response.

Attachments (1)

Xorg.0.log (27.3 KB) - added by greenfeld 3 years ago.
X server segfault

Download all attachments as: .zip

Change History (10)

comment:1 Changed 3 years ago by garysu

  • Summary changed from [CL2]Press many enter then write activity will hang up. to [CL2]Press enter many times in write activity and system will hang up.

comment:2 Changed 3 years ago by greenfeld

  • Action Needed changed from never set to diagnose
  • Component changed from not assigned to x window system
  • Owner set to jnettlet

The X server is dying after 4-5 pages of Write text, even if this is largely just single-character data.

Reproduced with 11.3.0 os883 on a B1 HS.

Changed 3 years ago by greenfeld

X server segfault

comment:3 follow-up: Changed 3 years ago by martin.langhoff

Any chance of a review of the log?

comment:4 in reply to: ↑ 3 Changed 3 years ago by garysu

Replying to martin.langhoff:

Any chance of a review of the log?

Hi Martin, when this issue appear and my CL2 cannot switch to terminal(Ctrl+Alt+F2 or F3), it hang up in sugar and cannot work anymore except press twice power button can normally shutdown system.
If you cannot duplicated this issue and you can close write then reopen it again. After you press many enter and this issue will appear soon.

comment:5 Changed 3 years ago by jnettlet

This is the proper bt. For some reason we are trying to _int_malloc a huge a mount of memory.

Thread 1 (Thread 0x405ee000 (LWP 774)):
#0  _int_malloc (av=0x4056c240, bytes=1079422976) at malloc.c:4439
#1  0x404a0498 in __libc_calloc (n=<value optimized out>, 
    elem_size=<value optimized out>) at malloc.c:4065
#2  0x0009f590 in eventToDeviceEvent (ev=0xbe8bb734, xi=0xbe8bb5f4)
    at eventconvert.c:557
#3  EventToXI2 (ev=0xbe8bb734, xi=0xbe8bb5f4) at eventconvert.c:228
#4  0x0003d090 in DeliverFocusedEvent (keybd=0x1f7df8, event=0xbe8bb734, 
    window=0x3c85c0) at events.c:3703
#5  0x000e2b04 in ProcessOtherEvent (ev=0xbe8bb734, device=0x1f7df8)
    at exevents.c:1104
#6  0x00100f44 in XkbHandleActions (dev=0x1f7df8, kbd=<value optimized out>, 
    event=0xbe8bb734) at xkbActions.c:1212
#7  0x000fd6cc in AccessXKeyboardEvent (keybd=0x1f7df8, 
    keyCode=<value optimized out>, isRepeat=1, type=2) at xkbAccessX.c:142
#8  0x000fd87c in AccessXRepeatKeyExpire (timer=<value optimized out>, 
    now=<value optimized out>, arg=<value optimized out>) at xkbAccessX.c:314
#9  0x0005bd1c in DoTimer (timer=0x39ce98, now=<value optimized out>, 
    prev=<value optimized out>) at WaitFor.c:420
#10 0x0005c364 in WaitForSomething (pClientsReady=0xbe8bb93c) at WaitFor.c:277
#11 0x0002e9b4 in Dispatch () at dispatch.c:368
#12 0x000234c8 in main (argc=8, argv=0x1be0c8, envp=<value optimized out>)
---Type <return> to continue, or q <return> to quit---
    at main.c:291

comment:6 Changed 3 years ago by jnettlet

This is interesting. So I have disabled all video acceleration and just used a raw framebuffer. I then started messing around and eventually recreated the problem. again the same a huge 1GB malloc, and everything is dead. Same place bck->fd = unsorted_chunks(av);

I have also found that if I then re-open a crashed write activity it crashes right away. It seems like this may be the odf format corrupting somehow.

comment:7 Changed 3 years ago by martin.langhoff

  • Action Needed changed from diagnose to test in build

Please test in OS25

comment:8 Changed 3 years ago by tonyforster

os25 did 11 pages of enter and no fault

comment:9 Changed 3 years ago by martin.langhoff

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.