First off, ScintillaNET v2.6 was installed as a control and I have been able to use it and compile, so I assume the installation is ok:
This app is targeting the full .NET 4.0 framework, not the client profile)
Environment variable
ScintillaNT folder content
The error message:
The code triggering the error:
The error happens on the second line when I "step-in" the load method. Looks completely unrelated, but highly reproducible: the error always happens at that exact step.
The problem turned out to be a corrupted XML file. I still don't know why the crash page was all about ScintillaNET, but it appears this had nothing to do with Scintilla.
I am not deleting this question because I could not find any indication that this could happen (errors in different parts of the code triggering a Scintilla error page) and it would have saved me a lot of time trying to track back the "scintilla" problem.
Related
For almost every page I open in Firefox, I see this error in the Console of the developer tool bar:
(!) The Components object is deprecated. It will soon be removed.
The source is the html page. It happens with pages I create, but also on many common websites.
I found this documentation on Components object on MDN web docs, but that does not clarify a lot. Note that even that page shows this message(!)
It looks like a warning, but according to the Console filter, it is an error.
My main questions are:
Is this something for me, as a developer of the page reporting this, to solve?
If so, how do I go about that?
I am not aware of any problems as a result of this. For now, that is.
I have seen this for over a year, maybe longer. I mostly ignore this, but every now and then it starts nagging me again. I don't want my code to break suddenly and would like to get rid of this message obscuring other messages.
This is not for the developer of the page to solve.
While biking back home, a possible cause popped up in my mind: could one of the add-ons I use cause this and yes, that appears to be the case.
I restarted with disabled add-ons and the message was gone.
Then I enabled them one at a time and the culprit is
Selenium IDE.
A bug report on this issue was closed with Won't fix, with the message:
This error will resolve itself when we move to a native app later this year.
In a MozillaZine topic of 2012, it is explained how it could have been solved.
The first one is just a warning that the addon is using "Components"
directly, which won't necessarily always be possible when using the
Add-on SDK. (The preferred way to do it is to access the aliases for
Components.classes and Components.interfaces and such that the SDK
provides by requiring the "chrome" module.) It shouldn't be a problem
right now, but might become one in the future.
it happened for me after installing Selenium plugin in my FireFox.
I created a new application with react native windows, and it works well the first (few) times I run it, however, when closing the application I always end up with the following warning:
Attempt by security transparent method 'System.Reactive.Concurrency.CoreDispatcherScheduler..ctor(Windows.UI.Core.CoreDispatcher)' to access security-critical type 'Windows.UI.Core.CoreDispatcher' failed.
I've tried this on more than one computer and all of them get the same error but I can't find a way to fix this, meaning I cant proceed with my Native project in fear that it will malfunction every day.
How do I fix this, to stop this from happening again, or is it a bug?
I'm a novice in React Native myself, but here are a few suggestions:
1) There's an issue logged in GitHub on this exact problem: https://github.com/Microsoft/react-native-windows/issues/1954
2) I personally find that I get this with command-line execution (react-native run-windows) but I don't think(?) that I've seen it when running from inside Visual Studio. Try that approach to running instead.
3) As described at GitHub - I've found that deleting windows\Debug folder before running tends to resolve the issue.
I am getting several (annoying) triggered breakpoints for my project that don't seem to correlate with any real actionable exceptions. I have removed all breakpoints from my project, the only one being the "exception breakpoint." The issue is, is that when I run my project, it is being triggered in the main function and does not provide much detail about where the exception occurred...I can usually just skip over it (usually a couple times) without any issue. This has only recently started happening, but I am having trouble tracking down the source of what's actually triggering the breakpoint. I'm running Xcode 6.1.1, but the issue hasn't always occurred with the particular version I am using. I have included some screenshots of my configuration/the triggered break point:
The issue was that I was listing a font in my Info.plist (Fonts provided by application) that was not part of the application bundle.
I am receiving random object reference error in different modules of my application.The errors m facing is intermittent. I did debug of my code it looks all correct. Moreover, whenever I run into that error and I try again (immediately after I got error) with same steps with same input conditions that error does not come up. This is something which is happening not only in in development regions but also in production regions. I tried to analyze and I got some leads that there might be problem with temporary ASP. But I don't know how that can cause object reference errors. Sometimes I see Source error information like App_Web_ighjds[some kind of ID I guess]. I don't know where exactly the problem is? As far as my code is concerned It looks all fine. I believe if there was problem with my code then it should be reproducible every time. Does anybody have any idea why such error might be happening? If it is issue with temporary asp.net files then what I should do to avoid such error?? Any help is much appreciated. Thanks.
You're looking for ideas: I would suspect your module initializers or any DI container initialization.
Look for code that runs only on application start.
I would recommend to reset your web server completely before starting new debugging session.
I would also recommend setting Visual Studio debugger to "Break when an exception is thrown", by going to "Exceptions" settings (Ctrl-Alt-E) and checking the "CLR Exception" "Thrown" checkbox.
I have just added ILCrashReporter-NG to my application to log application crashes. Unfortunately it seems to have broken my Sparkle updates (Sparkle gives an error when the appcast has downloaded and the Install button is clicked). I have added the ILCrashReporter launchReporterForCompany: report addr: method to applicationDidFinishLaunching. Does anyone have any experience of implementing these two frameworks together and if so, is this a problem that you encountered.
I use the two together without any problems. What's the error that you get? Did you change anything else besides adding Sparkle?
The only time I've had the update fail, as you describe, was after changing my bundle id so that the bundle id in the update and the application didn't match.