lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Frescobaldi Log Error -1073741819 on Windows10


From: Aaron Hill
Subject: Re: Frescobaldi Log Error -1073741819 on Windows10
Date: Thu, 27 Sep 2018 15:10:25 -0700
User-agent: Roundcube Webmail/1.3.6

Folks,

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?


-- Aaron Hill



reply via email to

[Prev in Thread] Current Thread [Next in Thread]