[etoys-notify] [JIRA] Commented: (SQ-1128) Clicking edge of Etoys window crashes Etoys

[Edward Mokurai Cherlin (JIRA)]

    [ http://tracker.squeakland.org/browse/SQ-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40986#action_40986 ] 

Edward Mokurai Cherlin commented on SQ-1128:
--------------------------------------------

This appears to be a problem only in Unity 3D. A fix for the related Scratch bug has been posted.

[Bug 1025013] Re: Resize scratch window, it doesn't update, goes black, and shrinks to a vertical strip in Unity-3D.

I can confirm that removing the -xshm option from /usr/bin/scratch
resolves the problem. The switch -xshm seems to work fine in 3D mode
(unity) on a secondary screen though. See attachment in bug #1072309

This also works for Etoys-to-go. Edit the etoys.sh script line

    VMOPTIONS="$VMOPTIONS -vm-display-x11 -xshm" 

to read


    VMOPTIONS="$VMOPTIONS -vm-display-x11"

>From a comment on the Scratch bug:

Here's the functionality of that command line switch:
"-xshm
enables the use of the X Shared Memory extension on servers that support it. This can dramatically improve display performance, but works only when Squeak is running on the server."

> Clicking edge of Etoys window crashes Etoys
> -------------------------------------------
>
>                 Key: SQ-1128
>                 URL: http://tracker.squeakland.org/browse/SQ-1128
>             Project: squeakland
>          Issue Type: Bug
>          Components: etoys-linux
>            Reporter: Edward Mokurai Cherlin
>
> In Etoys 5.0 on Ubuntu 12.04, clicking the window border, as if preparing to resize the window, can crash Etoys. As in bug SQ-1126 (crash on maximizing and then unmaximizing window), where screenshots are provided, the window may shrink sideways, ending up as a vertical line from which it can be difficult to quit. In some cases, Etoys appears to go into an endless loop. CPU usage is 100%, while Etoys fails to update the display. It may be necessary to kill the Etoys process externally.
> Error message in terminal:
> X Error: BadValue (integer parameter out of range for operation)
>   Major opcode of failed request:  12
>   Minor opcode of failed request:  0
>   Serial number of failed request: 4887
> X Error: BadValue (integer parameter out of range for operation)
>   Major opcode of failed request:  12
>   Minor opcode of failed request:  0
>   Serial number of failed request: 4888

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.squeakland.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira