Ticket #571 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

Sugar crash when stopping inactive Etoys

Reported by: FGrose Owned by: tomeu
Priority: Unspecified by Maintainer Milestone: Unspecified by Release Team
Component: Sugar on a Stick (SoaS) Version: 0.84.x
Severity: Unspecified Keywords:
Cc: bert Distribution/OS: Unspecified
Bug Status: New

Description

Observed with Soas-20090305 on Dell 8400 with 3 GByte of RAM

shell.log & webactivity-1.log attached

Attachments

tmpg6xDWy.txt Download (28.7 KB) - added by FGrose 4 years ago.
shell.log
tmpbpuG59.txt Download (9.5 KB) - added by FGrose 4 years ago.
webActivity-1.log
tmpQrxqoE.txt Download (3.6 KB) - added by FGrose 4 years ago.
shell log after sugar crash
shell.log Download (3.6 KB) - added by bert 4 years ago.
shell log with evidence of Sugar crash (BadWindow error)
tmphHgJWF.txt Download (7.0 KB) - added by FGrose 4 years ago.
slim.log after sugar crash

Change History

Changed 4 years ago by FGrose

shell.log

Changed 4 years ago by FGrose

webActivity-1.log

follow-up: ↓ 2   Changed 4 years ago by FGrose

This seemed to occur as the Etoys instance was closing. I hit the Frame|Etoys|Stop panel button at least 2 times as there was no feedback on its status.

in reply to: ↑ 1   Changed 4 years ago by FGrose

Replying to FGrose:

This seemed to occur as the Etoys instance was closing. I hit the Frame|Etoys|Stop panel button at least 2 times as there was no feedback on its status.

It was the first instance of Etoys opened on this machine. When I tried to reproduce, I noticed that Etoys stopped quickly, and I couldn't reproduce the fault.

  Changed 4 years ago by FGrose

  • cc bert added

Retesting with Soas1-20090319, and I tried to Stop the Etoys instance from its Frame panel 5 or 6 times with no apparent effect. When I tried to resume it from the same panel, the Frame instance disappeared, so it may have Stopped but not cleared its panel from the Frame. There was no X restart this time. (This was the first instance to run on this installation as well.)

Restarted Etoys to test again, the Frame label and panel behaviour is the same. This time I <Alt><Tab> to the Frame instance and it disappeared as when trying to resume from the panel, so Frame icon and panel seem not to have been dismissed after Stopping.

  Changed 4 years ago by FGrose

  • owner changed from tomeu to bert
  • summary changed from X restart after stopping multiple Browse instances and Etoys from Frame panels to Etoys fails to completely stop from Frame panel call
  • component changed from sugar to Etoys
  • version changed from Unspecified to 0.84.x
  • status_field changed from Unconfimed to New

Observed with Soas2-200905031329.iso installed with LiveUSB-creator3.6.5 onto this hardware,  http://www.smolts.org/client/show/pub_ee2f82d0-f863-454f-9d72-b1ee60fb3c65.

(Previously reported Browse involvement was superfluous.)

Steps to reproduce:

  1. Launch Etoys
  2. Switch to Journal
  3. Activate Frame
  4. From Frame Etoys panel, select Stop
    • Notice that Etoys icon remains
  5. From Frame Etoys panel, select Resume
    • Notice that you are switched to tty1 and then liveuser login

  Changed 4 years ago by bert

  • owner changed from bert to tomeu
  • status changed from new to assigned
  • component changed from Etoys to sugar
  • status_field changed from New to Unconfirmed

The Sugar crash in step 5 is worrying, but I cannot reproduce that crash in a recent SoaS beta running in Virtualbox, and in any case Sugar should not crash even if an activity was buggy. Assigning back to tomeu.

I can confirm the apparent hang in step 4. But once I activate Etoys (wether by clicking resume or pressing alt-tab) it stops normally. The likely cause for that is that the window-close event is not processed while Etoys is deactivated (by the Sugar D-Bus activate() call). Only once Etoys is activated again, the event is received and then the saving and exit is performed. This should eventually be fixed but I'd not consider it critical, stopping an activity while it is inactive is not a too frequent operation. I filed an upstream report nonetheless:
 http://tracker.squeakland.org/browse/SQ-233

  Changed 4 years ago by bert

  • summary changed from Etoys fails to completely stop from Frame panel call to Sugar crash when stopping inactive Etoys

Changed 4 years ago by FGrose

shell log after sugar crash

follow-up: ↓ 8   Changed 4 years ago by FGrose

Sugar crash observed with soas-beta.iso (14Apr2009) installed in VirtualBox2.2.2 disc with onboard livecd-iso-to-disk onto this hardware,  http://www.smolts.org/client/show/pub_f2cf5101-8203-4941-be03-408deedd03e5 on Win7-64 host.

shell log attached.

in reply to: ↑ 7   Changed 4 years ago by FGrose

Correction to !FGrose: VBox disc came from  http://www.sugarlabs.org/static/soas/soas-beta-1.zip (20Apr2009), run in VirtualBox2.2.2 on this hardware,  http://www.smolts.org/client/show/pub_f2cf5101-8203-4941-be03-408deedd03e5 on Win7-64 host.

  Changed 4 years ago by bert

This is odd. I used the same VDI (created 20 Apr 2009) and VirtualBox 2.2.2, although on a Mac. Does not crash here.

Changed 4 years ago by bert

shell log with evidence of Sugar crash (BadWindow error)

  Changed 4 years ago by bert

I could repro now - it only crashes when starting Etoys freshly, not when resuming an Etoys project (which is the default now). Sugar crashes with a BadWindow X error, presumably because in that case Etoys exits immediately when it receives the activate(true) call.

Changed 4 years ago by FGrose

slim.log after sugar crash

  Changed 4 years ago by FGrose

  • status_field changed from Unconfirmed to New

Reproduced also with soas-beta.iso (14Apr2009) booted directly from .iso in VirtualBox2.2.2 on Jackalope64 host.

slim.log attached

  Changed 4 years ago by bert

FWIW it does not crash in Sugar 0.82 (tested on an XO at build 800).

  Changed 4 years ago by tomeu

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

Fixed with help from Benjamin.

  Changed 3 years ago by sascha_silbe

  • distribution changed from SoaS to Unspecified
  • component changed from sugar to SoaS

Bulk change distribution=SoaS -> component=SoaS

Note: See TracTickets for help on using tickets.