<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Anyone here interested in this crash? Is there a newer VM I
should test with?<br>
</p>
<p>Thanks,</p>
<p>-Martin<br>
</p>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0" cellspacing="0"
cellpadding="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
</th>
<td>[Pharo-dev] Pharo 7 Repeatable crash: XIO: fatal IO
error 14 (Bad address) on X server ":0"</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
<td>Wed, 21 Feb 2018 10:37:18 -0800</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
<td>Martin McClure <a class="moz-txt-link-rfc2396E" href="mailto:martin@hand2mouse.com"><martin@hand2mouse.com></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Reply-To:
</th>
<td>Pharo Development List <a class="moz-txt-link-rfc2396E" href="mailto:pharo-dev@lists.pharo.org"><pharo-dev@lists.pharo.org></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
<td>Pharo Development List <a class="moz-txt-link-rfc2396E" href="mailto:pharo-dev@lists.pharo.org"><pharo-dev@lists.pharo.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>On the current Linux32 Pharo 7.0, (<a class="moz-txt-link-freetext" href="https://get.pharo.org/70+vm">https://get.pharo.org/70+vm</a> as of 30
minutes ago) the VM crashes with the message
XIO: fatal IO error 14 (Bad address) on X server ":0"
whenever I try to enlarge the Pharo window by dragging the corner, and
get to a size of about 2Mpixels. This is with a virgin image with no
windows open inside the main window. A workaround seems to be to open a
System Browser before resizing the main window.
This does not reproduce on Pharo 6.1 (<a class="moz-txt-link-freetext" href="https://get.pharo.org/">https://get.pharo.org/</a>).
This *does* reproduce when running the Pharo7 image on the Pharo 6.1 VM,
so it may not be entirely a VM problem.
Most times, no crash dump is created, and nothing is logged to
PharoDebug.log.
Occasionally, especially when rapidly changing the size of the window,
it segfaults and logs a dump. This may or may not be the same problem.
This is less annoying since I found the workaround, but still seems to
be something that should be fixed. Does anyone want further information
from me in order to fix it?
Regards,
-Martin
</pre>
</div>
</body>
</html>