Re: Frescobaldi Log Error -1073741819 on Windows10

[David Wright]

On Sun 30 Sep 2018 at 16:49:13 (+0100), address@hidden wrote:
> Date: Thu, 27 Sep 2018 15:10:25 -0700
> From: Aaron Hill <address@hidden <mailto:address@hidden>
> > 
> > An Access Violation has nothing to do with permissions as was stated
> > earlier.  This error code is specific to virtual memory management.  
> > 
> > Most often, this points to an error in programming logic such as a NULL
> > pointer access but it could be any attempt to read from and or write to a
> > virtual memory address that is invalid for the running process.
> > 
> > Based on threads earlier in the year, it would seem the Windows build of
> > LilyPond is known to have some gnarly and difficult to source issues with
> > memory management.  While it can often run without error, certain constructs
> > in input will result in an AV.  In fact, it is one of the reasons why I
> > stopped using the Windows build in favor of running the Linux version
> > through the Windows Subsystem for Linux (WSL).  Also, it would seem there
> > are very few and/or constrained resources for debugging this sort of thing,
> > as the principal developers for LilyPond would seem to be mostly
> > Linux-based.
> > 
> > Setting aside all that for a moment, Peter mentioned possible issues
> > manifesting in other software, and also that the input file in question has
> > worked before.  So the underlying issue most likely is caused by a recent
> > change to the system.  The fact that closing other running apps helped once
> > would make me think that there is an issue with excessive memory
> > consumption.  Programs that do not handle out-of-memory conditions well can
> > often run afoul of an AV.
> > 
> > @Peter: Would you kindly verify a few things?
> > - Does LilyPond work at all?  That is, are you only noticing issues with
> > particular input files or does it fail the same way even for simple inputs?
> > Also, is this issue occurring when building through Frescobaldi, or does it
> > also occur if you just launch LilyPond manually?
> > - Can you reproduce these issues when running LilyPond after a clean reboot
> > of the machine while running as little else as possible?
> > - Since this issue seems to impact two devices, have you installed anything
> > recently on both machines?  Also, have you made any configuration changes
> > that would have applied to both devices?
> 
> Sorry to be so long - I have been tangled up in Windows10.
> 
> First I have no issues with Lilypond or Frescobaldi. Clean reboots have
> removed MOST of the issues still one thing caught me out see below.
> 
> No configuration or download issues. But as usual file sharing on the local
> ethernet was spannered after the restores and continues to be here today and
> gone tomorrow.
> 
> The desktop needed a Windows10 style destructive restore losing my Outlook
> data files and all the Outlook pop and smtp data ( grrr) as well as a raft
> of other software. Who is it that relies only on Windows Store Apps!?.
> 
> I take your point and was coming to a similar conclusion.  I suspect the
> root of the problem may lie in the structure of the file index in Windows.
> There are two different observations.
> 
> a.    Somehow unbeknown to me I have got both onedrive and dropbox lurking
> about in the file index. This can lead to a file pointer effectively
> pointing to an empty folder (null) which can produce the above error
> message. I ended up with duplicate folder trees in and out of onedrive and
> one set of folders appears empty of files.
> b.    Secondly and possibly related some files were not accessible
> (permissions) and it was impossible to alter the permissions.
> c.    Could both a and b be the result of a corrupt file index?
> d.    The above is based on observation since I am ignorant of how the
> file index is created and where it is stored and how onedrive or dropbox
> interact with it.

It sounds to me as if you're grasping at straws here. I also find it
difficult to follow your terminology. How would you know where file
pointers are pointing, why an empty folder should appear as "null",
and why programs handling empty folders should throw access violation
errors or error -1073741819.

Point a. Switch off file sharing and networking: you should be able to
produce scores without requiring either.
Point b. Any system should have files that are inaccessible to users
without becoming root/superuser (appropriate to the system). Without
knowing which files and where they're located, this observation is
not helpful.
Points c and d. If you're worried about the state of the filesystem
"structure" (as opposed to the files' contents), you should run the
windows filesystem-checking tools as appropriate.

(I'm assuming that your applications are actually installed on your
computers and that you are only using facilities like onedrive and
dropbox for storing/sharing data files.)

Cheers,
David.