Subject:StylusStudio Crashes when idling.. Author:Ken Jenson Date:16 Mar 2006 05:21 PM
We have just purchased and activated your Professional Version and I have received a few ‘GPF’ errors and lost work the first time. Now I save every few minutes or so.
The error box information follows and it will pop up while I am away from my desk, perhaps during an autosave??
____
Runtime Error!
Program: ...../bin/struzzo.exe
R6025 - pure virtual function call
_________
Do you have a solution for this issue? We are heading into a heavy development cycle and cannot afford to have this happening.
Subject:StylusStudio Crashes when idling.. Author:Minollo I. Date:22 Mar 2006 09:52 PM
Can you also tell us what editors you have typically open when that happens (and, in particular, which one is the active one)? XML editor? XSLT? XSLT WYSWIYG?
Subject:StylusStudio Crashes when idling.. Author:Minollo I. Date:23 Mar 2006 12:41 PM
Ken,
we are struggling to understand what may be going wrong; it's also strange that the crash log file (struzzo.dmp) is empty.
A few other questions:
- the files that you have typically open in Stylus Studio, are they stored locally on your file system? Or available on the network?
- what Windows version/SP level are you running?
- do you have a screen saver configured that would kick in after a while that you leave your machine idle? If yes, which one and do you need a password to go back to your desktop?
Subject:StylusStudio Crashes when idling.. Author:Ken Jenson Date:23 Mar 2006 01:02 PM
My answers below:
A few other questions:
- the files that you have typically open in Stylus Studio, are they stored locally on your file system? Or available on the network?
>>>>>The local file system
- what Windows version/SP level are you running?
>>>>>Windows XP, Media Center Edition 2002, SP 2
- do you have a screen saver configured that would kick in after a while that you leave your machine idle? If yes, which one and do you need a password to go back to your desktop?
>>>>>No Screensaver
A couple of other tidbits:
I am generally running IE windows, Outlook 2002, and MS Visual Studio at any given time.
Subject:StylusStudio Crashes when idling.. Author:Minollo I. Date:23 Mar 2006 01:23 PM
Do your XML documents reference XML Schema schemas?
Does the crash *always* happen when you leave Stylus Studio idling for a while?
A couple of things to try:
- In Tools > Options > Application Settings make sure that "Automatically save modified files every X minutes" is disabled
- In Tools > options > XML Editor > XML Settings enter 300000 in the SenseX-Refresh Interval field
Subject:RE: StylusStudio Crashes when idling.. Author:David Karr Date:23 Mar 2006 01:55 PM
Would it be useful to know what file I/O was happening just before the
crash? That is, what files or directories were being accessed, not
necessarily what they were writing or reading. If so, they could
install the "Filemon" tool from the Sysinternals web site and just let
it run. Once Stylus Studio dies, the last log entries in Filemon will
show what files/directories were being referenced.
> -----Original Message-----
> From: stylus-studio-tech Listmanager
> [mailto:stylus-studio-tech.listmanager@stylusstudio.com]
> Sent: Thursday, March 23, 2006 10:26 AM
> Subject: StylusStudio Crashes when idling..
>
>
> From: Minollo I.
>
> Do your XML documents reference XML Schema schemas?
> Does the crash *always* happen when you leave Stylus Studio
> idling for a while?
>
> A couple of things to try:
> - In Tools > Options > Application Settings make sure
> that "Automatically save modified files every X minutes" is disabled
> - In Tools > options > XML Editor > XML Settings
> enter 300000 in the SenseX-Refresh Interval field
>
> Minollo
>
>
> --
> To reply: mailto:stylus-studio-tech.14393@stylusstudio.com
> To start a new topic: mailto:stylus-studio-tech@stylusstudio.com
> To login: http://www.stylusstudio.com/SSDN/
> To (un)subscribe:
> mailto:stylus-studio-tech.list-request@stylusstudio.com
>
>
Subject:RE: StylusStudio Crashes when idling.. Author:Minollo I. Date:23 Mar 2006 01:58 PM
Sure; but applying the suggested changes should shutdown all I/O activities; if the problem goes away doing that, then we can focus on which I/O activity is the culprit.