Search Issue Tracker
Fixed in 4.5.1
Votes
5
Found in
4.3.4f1
Issue ID
593423
Regression
No
Calling Physics2D.OverlapCircleNonAlloc() crashes WP8 application
Steps to reproduce:
1. Create a project which uses Physics2D.OverlapCircleNonAlloc() function. Described here: http://docs.unity3d.com/Documentation/ScriptReference/Physics2D.OverlapCircleNonAlloc.html
2. Build and run on Windows Phone 8 device
3. Application will crash reporting Access Violation Exception at Physics2D.OverlapCircleNonAlloc()
Comments (4)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
shopguy
May 15, 2014 04:36
Physics2D.OverlapPointNonAlloc crashing for me on Windows Store apps using latest version of Unity. I get red text in the console for every call that just reads "outHits", then eventually, after a few seconds worth of calls on every frame, I get an Access Violation and app crashes.
Gogeric
May 09, 2014 07:24
That seems to be always happening i have less than 5 colliders on scene and i provide an array of 20 colliders, same error on windows phone... this function not working on windows phone is really breaking one of the places where it had most interest of being not allocated
yuri_opolev
Apr 27, 2014 18:57
Also calling Physics2D.OverlapPointNonAlloc() crashes WP8 application.
KeeWeed
Apr 13, 2014 10:30
I believe it only happens when the array that is passed by argument is too small for the number of results.