Maybe related to this bug.
I receive a NotImplementedException for the following line:
serviceBusClient <- new ServiceBusClient(connectionString) // NotImplementedException
The context is as follows:
open Azure.Messaging.ServiceBus
...
let mutable serviceBusClient : ServiceBusClient = null
...
serviceBusClient <- new ServiceBusClient(connectionString) // NotImplementedException
IAsyncDisposable:
I received the same exception when removing the "new" declaration since the class no longer implemented IDisposable, but rather IAsyncDisposable:
serviceBusClient <- ServiceBusClient(connectionString) // NotImplementedException
Additional Information:
I was unable to reproduce this anomaly in a separate integration test (NUnit)
I only observe this anomaly when running a Xamarin.Forms app using the Android emulator
The same code was working two months ago
Originally observed exception using Azure.Messaging.ServiceBus version 7.3.0 (Nuget)
Also observed exception using Azure.Messaging.ServiceBus version 7.1.2 (Nuget)
Using .NetStandard 2.1
I increased output verbosity to Diagnostics without observing any additional clues
Azure.Messaging.ServiceBus (version 7.0 works)
QuickWatch:
Call Stack:
Related
When an exception occurs in debug mode. I would quite often go back to the previous line with the yellow debugger arrow, edit the code, then keep running step by step.
It seems that now when some kind of exceptions are thrown, it's not possible to move the debugger cursor until the exception has been caught. Is there a workaround to make this work again?
That makes the progress of quick testing much more difficult.
EDIT:
This appeared after updating to vs 16.8 (then 16.8.1)
Issue occurs with .NET 5 or .NET 3.1, or .NET framework 4.7.2, not a framework issue
I uninstalled Resharper to rule this out
if I just do throw new exception("Pause"); or do a divide by zero it will not cause the issue.
if it is involving Sytstem.Linq then I will have the issue.
Example:
using System;
using System.Linq;
namespace TestDebug
{
class Program
{
static void Main(string[] args)
{
Console.WriteLine("Hello World!");
int[] test = null;
var error = test.Any();
Console.WriteLine("Bye bye World!");
}
}
}
EDIT2:
The tooltip is different in my example from what I would see with a different exception such as a divide by zero exception. (see comment).
The tooltip when I can't drag the cursor is saying:
"This is the next statement to execute when this thread returns from the current function"
It does not suggest to drag the cursor as it would normally do
I am working on a DirectX 11 app and I am having difficulties creating an instance of IDXGIFactory7. I could not find a CreateDXGIFactory7() function so I am using CreateDXGIFactory2() like this:
IDXGIFactory7* factory;
HRESULT hr = ::CreateDXGIFactory2(DXGI_CREATE_FACTORY_DEBUG, __uuidof(IDXGIFactory7), (void**)&factory);
The difficulty I am having is that this call throws an exception when attempting to use the graphics debugger in Visual Studio 2019. I also tried IDXGIFactory6 which also throws an exception. If I change it to IDXGIFactory2 it works and I can use the graphics debugger.
This code does run and debug fine using the regular debugger, but not the graphics debugger. I get the following exception:
Exception thrown at 0x00007FFAE1513B29 in DirectXTemplated.exe: Microsoft C++ exception: GRFXTool::ToolException at memory location 0x0000004D28BFE010.
I downloaded the sample from https://www.3dgep.com/introduction-to-directx-11/ and modified it to use IDXGIFactory7 and CreateDXGIFactory2() instead of IDXGIFactory in the QueryRefreshRate() function. You will need to set g_EnableVSync = TRUE at the top of main.cpp for it to create the factory. This does generate the exception when attempting to use the graphics debugger.
This is a Windows 10 Pro x64 installation with Visual Studio v16.7.6.
Based on the comment from Roman R., the way to get around the problem seems to be to use CreateDXGIFactory2() to create an IDXGIFactory2 and use QueryInterface() on that to obtain the one for IDXGIFactory7.
Doing it this way avoids the exception and the app runs under the graphics debugger without issue.
I'm working on a React Native 0.40 app that uses Realm JS 1.0.0. I am experiencing crashes when reading/writing and some odd behaviors. For example, one of the crashes only happens when I add a second record to the table.
When it crashes, the output prints:
<Error>: MY_APP(18085,0x7000075ce000) malloc: *** mach_vm_map(size=18446744073345937408) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
(this is on the iOS simulator)
I've worked with Realm in Swift projects in the past where I had to be aware not to pass objects or collections around and also to not use the same realm from multiple threads, etc. However, I don't think those issues apply to RN. Right?
My general approach is to have a Realm factory like:
realm.js
export function getUserRealm(){
const realm = new Realm({
schema: combinedSchemas,
path: `main.realm`
});
console.log( "💿 User Realm Path:", realm.path );
return realm;
}
Then I call getUserRealm() from wherever it is that I'm using realm.
There are a few places where I do pass Results between functions and callbacks.
The main question is, what should I guard against in order to prevent crashes?
I'm running a Grails application in "PRODUCTION ENV." with version 2.3.1. It runs fine for some time. But after some time, it starts failing with exception "InvalidDataAccessApiUsageException". Again when I delete target folder and re run the application, it works good.
There is no error while working in "DEVELOPMENT ENV".
Detailed exception is
[[ErrorType:class org.springframework.dao.InvalidDataAccessApiUsageException],
[ErrorMessage:The given object has a null identifier: com.test.model.Test;
nested exception is org.hibernate.TransientObjectException:
The given object has a null identifier: com.test.model.Test]]
I'm geting following exception while extracting Twitter data using Flume on CDH4.
twitter4j.TwitterStreamImpl: Receiving status stream. Exception in
thread "Twitter4J Async Dispatcher[0]" java.lang.NoSuchMethodError:
twitter4j.json.JSONObjectType.determine(Ltwitter4j/internal/org/json/JSONObject;)Ltwitter4j/json/JSONObjectType;
at
twitter4j.AbstractStreamImplementation$1.run(AbstractStreamImplementation.java:100)
at
twitter4j.internal.async.ExecuteThread.run(DispatcherImpl.java:116)
I was getting the same issue in my code, but when I changed the .jar from twitter4j-core-2.2.6.jar to twitter4j-stream-3.0.0.jar it got resolved.
The main reason behind this issue was due to FilterQuery fq = new FilterQuery(); was used in the code and FilterQuery class is present in twitter4j-core-2.2.6.jar but it has some problem and due to this the issue was coming. If we replace the twitter4j-core-2.2.6.jar with twitter4j-stream-3.0.0.jar then it also contains FilterQuery class and issue gets solved.