Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

WP8 - SEHException thrown by CoronaLabs.Corona.DotNet.dll
Started by spacewolf Jan 01 2015 07:25 PM

1 reply to this topic
error wp8 exception sehexception
[TOPIC CONTROLS]
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

spacewolf

[GLOBAL: userInfoPane.html]
spacewolf
  • Contributor

  • 298 posts
  • Enterprise

Hey guys,

 

I'm preparing my latest game for windows phone 8 and ran into this exception:

 

System.Runtime.InteropServices.SEHException was unhandled
Message: An unhandled exception of type 'System.Runtime.InteropServices.SEHException' occurred in CoronaLabs.Corona.DotNet.DLL
Additional information: External component has thrown an exception.
 
I got it during the normal game play of my app.
 
My app uses about 34 MBs of texture memory on my lumia 920 phone.
 
I noticed that as I continue to play game rounds the app gets slower and slower in its response to input touches (looks to me like maybe 500 milliseconds - 1 second for a touch response), and then it died with the exception above. I don't spot any memory leaks, at least for the texture memory.
 
I'm wondering if you know what this is or have seen it before?
 
As a note the app works perfectly on iOS and Android :)
 
Thanks!
 
CoronaCards WP8 version = 14.0.2511


[TOPIC: post.html]
#2

Joshua Quick

[GLOBAL: userInfoPane.html]
Joshua Quick
  • Moderator

  • 3,397 posts
  • Corona Staff

Are you sure you are not leaking objects on the Lua side?

 

You can track how much memory is used by Lua via the following function call...

   local memoryUsedInKB = collectgarbage("count")

 

Would you mind running the above on a timer (perhaps every 10 seconds) and print it to Visual Studio's log?

I ask because I'm not aware of any memory leaks.  I'm also wondering if somewhere in your code you might be using an API that's not supported, it's causing a Lua runtime error that's getting caught, but is leaking a Lua object.  If there is a Lua runtime error, you should be able to see it in Visual Studio's "Output" panel.




[topic_controls]
[/topic_controls]