LINQPad - Unhandled Thread Exception

edited April 2018
From time to time, when I left linqpad idle, I'm presented with several windows saying:
LINQPad - Unhandled Thread Exception:
An exception has been thrown on a user-create thread.
System.NullreferenceException: Object reference not set to an instance of an object.
I'd like to solve my issue, but the information about the crash is too vague.

Right now I don't know how to reproduce it, but I'm sure, my code is not running at the moment of crash.
Is there any debug info or anything I can provide ?

I have several other 3rd party Data Context Providers installed:
CSV Context Driver
PostreSQL (LINQ to DB)
IQ
Linq2Azure
I didn't try to uninstall one of these and test ...
I think I have this issue more than half a year (not sure, but quite a long time), so it crosses several LINQPad versions.

Comments

  • Go to %localappdata%\linqpad\logs. You should find more details written to the log.txt file. If the problem is not self-evident, post the details here.
  • Today I've encountered this error.
    I've got 8 same windows with error message
    System.NullReferenceException: Object reference not set to an instance of an object.

    Version v5.28.04(AnyCPU)

    This is the content of the log.txt file
    5.28.04(AnyCPU) 2018-04-19T17:56:45.1515207+02:00 Execution tracking deadlock 5.28.04(AnyCPU) 2018-04-19T17:57:24.5219646+02:00 Execution tracking deadlock 5.28.04(AnyCPU) 2018-04-23T15:53:06.7382394+02:00 Execution tracking deadlock 5.28.04(AnyCPU) 2018-04-24T16:47:44.1339957+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:47:44.1730329+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:47:44.2020654+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:47:44.2340955+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:47:44.2651251+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:47:44.2991600+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:48:13.5269332+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:48:13.5879948+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:48:13.6625694+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:48:13.7111152+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:48:13.7846847+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.28.04(AnyCPU) 2018-04-24T16:48:13.8497467+02:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data:
  • The exceptions that you've posted don't have a stack trace, which is very unusual. Can you confirm that there's no copy-and-paste error?
  • Yes, that's correct. No copy paste error.

    This is dump of the log.txt
    https://gist.github.com/hopp/eb5e6816f5efb30a4312ed35be0d966d
  • Hi Joe,
    I've got another one.

    Linqpad Crashed with this exception:
    System.NullReferenceException: Object reference not set to an instance of an object.
    
    Whole log. txt can be found here:
    https://gist.github.com/hopp/052de2980f56dea021768113369c7b76

    I think those "normal" exceptions with stack traces are valid.
    I made some stupid huge queries and tested our internal nuget server.

    What I've done recently is, that I worked remotely via RDP.
    But I don't have this tested yet.
  • I have been having the same error for about a year across LinqPad with the same exact logged message. Usually it happens when I resume from sleep or from idle. The linqpad window has that exact same message posted. It often doesn't even make the appdata logs. This is really a hassle
  • I take it you haven't disabled process isolation? (You can check by ensuring that after running a query, a message appears at the right of the status bar indicating the process ID "PID=n").
  • Yes, I can confirm, that there is PID=number in the lower right corner after running query.
    Also in Task Manager I can see
    LINQPad 5
    and as many YourLINQPad Query processes (with process name LINQPad.UserQuery.exe)
    as I have opened queries.
  • Just happened again. I was working in a session, nothing went into sleep or otherwise.

    Faulting application name: LINQPad.EXE, version: 5.26.1.0, time stamp: 0x5a0d5cb5
    Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x4736733c
    Exception code: 0xc000041d
    Fault offset: 0x0000000000013fb8
    Faulting process id: 0x21e0
    Faulting application start time: 0x01d3f3acf18036c9
    Faulting application path: C:\Program Files (x86)\LINQPad5\LINQPad.EXE
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: 9b179575-6c7d-437f-bdbe-4e139e99349c
    Faulting package full name:
    Faulting package-relative application ID:

    Event ID 1000
    Faulting application name: LINQPad.EXE, version: 5.26.1.0, time stamp: 0x5a0d5cb5
    Faulting module name: System.Windows.Forms.ni.dll, version: 4.7.2556.0, time stamp: 0x59b8360c
    Exception code: 0xc0000005
    Fault offset: 0x00000000008c6d56
    Faulting process id: 0x21e0
    Faulting application start time: 0x01d3f3acf18036c9
    Faulting application path: C:\Program Files (x86)\LINQPad5\LINQPad.EXE
    Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\521c34e277f9c9e0fc16511eaf6a448e\System.Windows.Forms.ni.dll
    Report Id: 0bbd4454-4b66-4443-a2eb-b3e3bb5756f1
    Faulting package full name:
    Faulting package-relative application ID:

    Event ID 1026
    Application: LINQPad.EXE
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.NullReferenceException

    and maybe this one:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {D63B10C5-BB46-4990-A94F-E40B9D520160}
    and APPID
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
  • Same error happening here. I am using the 5.31.00 AnyCPU release.

    5.31.00(AnyCPU) 2018-07-18T11:46:09.2778061-04:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data: 5.31.00(AnyCPU) 2018-07-18T11:46:09.3423040-04:00 Thread exception - NullReferenceException: Object reference not set to an instance of an object. First chance data:

    That repeats many times each time it occurs and I end up with a report error dialog for each one.

    Good news, though: it always successfully recovers my queries!
  • edited October 1
    Was there any progress on the above issues? Unsure if related, but I got the following NullReferenceException that crashed LinqPad overnight and ended up in the Log. Unlike the above, there is a trace leading to LINQPad.Program.Run. The machine was running LinqPad 5.36.03.
    5.36.03 2019-10-01T03:38:17.4208256+10:00 Thread exception - 
    NullReferenceException: Object reference not set to an instance of an object.
    
    First chance data: LINQPad.Program.Run(queryToLoad,runQuery,activationCode,activateAll,deactivate,noForward,noUpdate,caller) offset=0x27C
       -LINQPad.Program.Go(args) offset=0x763
       -LINQPad.Program.Start(args) offset=0xA3
       -LINQPad.ProgramStarter.Run(args) offset=0x12
       -LINQPad.Loader.Main(args) offset=0x2B4
  • The above issues were fixed in 5.33. The stack trace for the error that you just reported indicates something different - the NRE looks like it was thrown during the shutdown phase, possibly after some critical error.
  • I think you are right that this was a secondary error. Running LinqPad using legacycorruptedstateexceptionspolicy = true, a dialogue box appeared (screenshot attached) during a long-running query (which continued running) to show a NullReferenceException. No stack trace.

    It was only when I closed the dialogue box that LinqPad crashed. I found the NullReferenceException I posted above in the log and assumed it was the same that had been displayed in the dialogue box, however in retrospect they're probably two distinct errors.

    In that case the original error is probably that FileSystemWatcher one that we've previously discussed over support.


Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!