Hi,

recently (couple of days ago) sometimes when I start Pharo there's a box at the 
bottom "Debug console" with the following info

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Debug console
# To close: F2 -> 'debug options' -> 'show output console'
# To disable: F2 -> 'debug options' -> 'show console on errors'
LoadLibrary(SurfacePlugin) (998: Invalid access to memory location.

)
LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location.

)
LoadLibrary(SurfacePlugin) (998: Invalid access to memory location.

)
LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location.

)
LoadLibrary(SurfacePlugin) (998: Invalid access to memory location.

)
LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location.

)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I have Windows 10 & VM Version: Cog Spur VM 5.0 (release) from Feb  3 2017 
(downloaded from files.pharo.org)

This error results in Athens (and Roassal) not working, although Pharo itself 
seems fine.

Reopening the image has no effect, and the only resolution is to do a system 
reboot.


There is also crash.dmp from Feb 12 (possibly the day it started) containing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sun Feb 12 23:10:24 2017

Exception code: C0000005
Exception addr: 0040BDD0
Access violation (write access) at 00AFF43C
EAX:FFFFFFFF    EBX:74329850    ECX:549D7EBE    EDX:00AFF43C
ESI:74315F70    EDI:00489DB9    EBP:0887FF94    ESP:0887FF54
EIP:0040BDD0    EFL:00010206
FP Control: 0000027F
FP Status:  00000000
FP Tag:     0000FFFF


Crashed in some other thread
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Makes me wonder whether the SurfacePlugin.dll didn't somehow get corrupted... 
but then again there's no modification date change on the dll file, nor would 
it explain why rebooting fixes it.

Thanks,
Peter

Reply via email to