Skip to content
This repository was archived by the owner on Mar 19, 2019. It is now read-only.

GetContextAsync Exceptions on ARM #126

Closed
Tratcher opened this issue Jun 15, 2015 · 7 comments
Closed

GetContextAsync Exceptions on ARM #126

Tratcher opened this issue Jun 15, 2015 · 7 comments
Assignees

Comments

@Tratcher
Copy link
Member

When running on Win 10 IoT with ARM CoreCLR we often get the following error:

error   : [Microsoft.Net.Http.Server.WebListener] GetContextAsync
Microsoft.Net.Http.Server.WebListenerException: Invalid access to memory location
   at Microsoft.Net.Http.Server.WebListener.GetContextAsync()
error   : [Microsoft.AspNet.Server.WebListener.MessagePump] ListenForNextRequestAsync
Microsoft.Net.Http.Server.WebListenerException: Invalid access to memory location
   at Microsoft.Net.Http.Server.WebListener.GetContextAsync()
   at Microsoft.AspNet.Server.WebListener.MessagePump.<ProcessRequestsWorker>d__18.MoveNext()

This looks similar to: http://blogs.msdn.com/b/cie/archive/2013/10/31/compute-emulator-invalid-access-to-memory-location.aspx

@Tratcher Tratcher added the bug label Jun 15, 2015
@Tratcher
Copy link
Member Author

Possibly related: aspnet/dnx#2063

@munyirik
Copy link

Any update on this? I'm trying to use WebListener on my Raspberry Pi 2 and hit this issue.

@moozzyk
Copy link
Contributor

moozzyk commented Apr 26, 2016

@muratg - this may need to be retriaged.

@muratg muratg modified the milestones: 1.0.0, Backlog Apr 26, 2016
@muratg
Copy link

muratg commented Apr 26, 2016

Let's reconsider this in 1.0.0 since UWP apps can now use http.sys to server web requests.

@munyirik
Copy link

Thanks. What's the timeline for 1.0.0?

@moozzyk
Copy link
Contributor

moozzyk commented Jun 8, 2016

The issue here is that HttpReceiveHttpRequest expects the buffer to be 8-byte aligned but on ARM the buffer is 4-byte aligned and when falls on the 4 byte boundary HttpReceiveHttpRequest returns ERROR_NOACCESS which is then converted to the "Invalid access to memory location" exception.

moozzyk pushed a commit that referenced this issue Jun 15, 2016
moozzyk pushed a commit that referenced this issue Jun 15, 2016
moozzyk pushed a commit that referenced this issue Jun 17, 2016
moozzyk pushed a commit that referenced this issue Jun 22, 2016
@moozzyk
Copy link
Contributor

moozzyk commented Jun 22, 2016

Fixed in f63e53b

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants