Momory access violation

Do you have a planned release date for fixed version?

Hi,

Thanks for this. I have tested and it appears to be working now.

Magnus

(Sorry, I'm mixing up the input to my two cases. Copying the info below
from the hanging app case.)

I received your note about testing version 1602r. The link was to my other
case, but I received an error message that may be of value for this case:

Access violation
File - C:\Program Files\PushOk Software\SVNSCC\svn\svncom.dll
Offset - 0x00016be8 Line 635

This actually happened with only one Word document open. I have also got
the same error message with two documents open as well, so it probably
doesn't have anything to do with the number of documents. But the access
violation doesn't happen as often as before. The progress dialog displays:

Get extended info for : C:\dev\svnws\r1\model1

Hi,

Because of the problems in this case:

http://www.pushok.com/tickets_addmodify.php?id=2220

I have disabled both "Show progress dialog for operation longer than..."
and "Close progress dialog window in...".

/Magnus

I should also mention that we haven't had this problem when working with
the previous SVNSCC version 1.5.1.3.

Hi,

Working with our customer, I have been able to reproduce these memory
access violations. Using our application WayPointer, it happens every time
we are working with four files open from the work space: a project file, a
model file, and two Word documents. If we only have one Word document open
we don't see the error.

It's difficult to explain the scenario because WayPointer is a rule
evaluation engine the evaluates many rules in a background thread,
including rules that check on the SCC status of the currently open files.
The results of the rule evaluations are recommendations to the user to
check in or check out files.

So, when the user is working with two Word documents at the same time, the
memory access violation occurs in the SccOpenProject call. This I have been
able to reproduce each time. I don't know if this will help you, but we do
need help tracking down this error.

Thanks,
Magnus

Hi,

We are calling the SCC api from our application WayPointer. WayPointer is
written in C# (managed code), and is calling SVNSCC functions (unmanaged
code). A customer is reporting memory access violations from the SVNSCC
calls. The errors occur now and then, intermittently. Here is an example
call stack:

Attempted to read or write protected memory. This is often an indication
that other memory is corrupt.

Exception type: System.AccessViolationException

Source: SccIntegration

Thread: EvaluationEngine

Stack trace:

at WayPointer.SccIntegration.SccOpenProjectInvoker.Invoke(UIntPtr
ppvContext, IntPtr hWnd, StringBuilder lpUser, StringBuilder lpProjName,
StringBuilder lpLocalProjPath, StringBuilder lpAuxProjPath, String
lpComment, TextOutProcCallback lpTextOutProc, Int32 dwFlags)

at WayPointer.SccIntegration.SccAPI.SccOpenProject(UIntPtr ppvContext,
IntPtr hWnd, StringBuilder lpUser, StringBuilder lpProjName, StringBuilder
lpLocalProjPath, StringBuilder lpAuxProjPath, String lpComment,
TextOutProcCallback lpTextOutProc, Int32 dwFlags)

at WayPointer.SccIntegration.SccClient.OpenProject()

at WayPointer.WayPointerSccServer.WayPointerSccServer.QueryStatus(String
fullpath)

at
WayPointer.WayPointerSccServer.WayPointerSccServer.IsSourceControlled(String
fullpath)

at
WayPointer.RulePackage.FileIsNotVersionControlled.FindConclusions(AgentInstance
agent, Hashtable _contextBinders, JRLCollection _environment,
EvaluationTask _evaluationTask)

at
WayPointer.ApplicationManagement.PrecedenceRule.FindConclusions(Hashtable
context, EvaluationTask task)

at
WayPointer.ApplicationManagement.EvaluationEngine.EvaluationTimer.FindConclusions()

at
WayPointer.ApplicationManagement.EvaluationEngine.EvaluationTask.FindConclusions()

at
WayPointer.ApplicationManagement.EvaluationEngine.EvaluationTask.Evaluate()

at
WayPointer.ApplicationManagement.EvaluationEngine.EvaluationTaskScheduler.EvaluateOneTask()

at
WayPointer.ApplicationManagement.EvaluationEngine.EvaluationEngine.RunEngineThread()


The explanation for exception System.AccessViolationException is as
follows:
http://msdn.microsoft.com/en-us/library/ms164911(VS.80).aspx

An access violation occurs in unmanaged or unsafe code when it attempts to
read or write to memory that has not been allocated, or to which it does
not have access. Not all reads or writes through bad pointers lead to
access violations, so an access violation usually indicates that several
reads or writes have occurred through bad pointers, and that memory might
be corrupted.

In managed code, all references are either valid or null. Any operation
that attempts to reference a null reference in verifiable code throws
NullReferenceException.

An access violation that occurs in unsafe managed code can be expressed as
either a NullReferenceException or a AccessViolationException, depending on
the platform.

Access violations in unmanaged code that bubble up to managed code are
always wrapped in an AccessViolationException.