- Home
- Forum
- ASP.NET Core - EJ 2
- Getting a System.StackOverflowException When Uploading Files
Getting a System.StackOverflowException When Uploading Files
Hello,
I'm currently getting a System.StackOverflowException whenever I attempt to upload a file using the File Manager, combined with a slightly customized AzureFileProvider (I had to modify several of the class methods to implement revolving azure access keys that we have implemented on our storage account)
Most if not all functions seem to be working fine except actually uploading files.
The Overflow appears to be happening very early on in the post lifecyle shortly failing directly after all middleware has been called. I get the error on the awaiter for _next on my last custom middleware implementation.
My base controller get's hit and I can unwrap the httpcontext (nothing looks unusual) then my middleware get's instantiated and fails before moving out to execute the called method on my FilesController.
Very strange and I'm not getting much out of tracing the callstack and of course the exception details are barren.
The application is currently targeting .Net Core 2.2 and I am using as of this writing the latest nuget for syncfusion.
Thank you for any input.
I'm currently getting a System.StackOverflowException whenever I attempt to upload a file using the File Manager, combined with a slightly customized AzureFileProvider (I had to modify several of the class methods to implement revolving azure access keys that we have implemented on our storage account)
Most if not all functions seem to be working fine except actually uploading files.
The Overflow appears to be happening very early on in the post lifecyle shortly failing directly after all middleware has been called. I get the error on the awaiter for _next on my last custom middleware implementation.
My base controller get's hit and I can unwrap the httpcontext (nothing looks unusual) then my middleware get's instantiated and fails before moving out to execute the called method on my FilesController.
Very strange and I'm not getting much out of tracing the callstack and of course the exception details are barren.
The application is currently targeting .Net Core 2.2 and I am using as of this writing the latest nuget for syncfusion.
Thank you for any input.
SIGN IN To post a reply.
3 Replies
1 reply marked as answer
SP
Sowmiya Padmanaban
Syncfusion Team
August 12, 2020 10:45 AM UTC
Hi HDusten,
We have checked your reported upload issue with FileManager component. It is a known issue from our end and we have considered this as a bug from our end. This bug fix will be included in our Volume 3 Release which is expected to be released at the end of September 2020. Until then, track the below feedback link for bug status.
This issue occurs due to framework limitations, since the upload functionality of FileManager component will be working fine in .NET Core 2.1 and recent .NET Core3.0 versions. So, we suggest you to use the .NET Core 3.1.
For your reference, we have prepared a sample for FileManager component with .NET Core 3.0. All the functionalities of FileManager component will be working fine in the below sample.
We appreciate your patience.
Regards,
Sowmiya.P
Marked as answer
HD
HDusten
September 4, 2020 09:09 PM UTC
Thank, we ended up just doing the migration to 3.1 and the plugin is working well.
SP
Sowmiya Padmanaban
Syncfusion Team
September 7, 2020 07:49 AM UTC
Hi HDusten,
We are happy to hear that your application works fine with .NET 3.1 version. As promised in our last update, we will include the fix for the .NET 2.2 version issue with Volume 3, 2020 release.
We appreciate your patience.
Regards,
Sowmiya.P
SIGN IN To post a reply.
- 3 Replies
- 2 Participants
- Marked answer
-
HD HDusten
- Aug 11, 2020 05:33 AM UTC
- Sep 7, 2020 07:49 AM UTC
