Opened 15 years ago
Closed 2 years ago
#1150 closed defect (fixed)
Instability in .net Wrapper for MgLayerCollection
| Reported by: | crispinatime | Owned by: | jng |
|---|---|---|---|
| Priority: | low | Milestone: | 4.0 |
| Component: | Web API | Version: | 2.1.0 |
| Severity: | minor | Keywords: | |
| Cc: | External ID: |
Description
Hi,
Using the MgLayerCollection I regularly get an "Unhandled Exception" (about once every 20 calls) to the .Clear() and .RemoveAt() methods.
I have implemented a different object collection as a work-around in my app ... but below is the message within the exception thrown from 2.1.0.4283
Crispin
MgLayerCollection_Clear() line 680 file .\MgApi_wrap.cpp MgLayerCollection_RemoveAt() line 680 file .\MgApi_wrap.cpp
Change History (9)
comment:1 by , 13 years ago
| Milestone: | → 2.4 |
|---|
comment:2 by , 12 years ago
| Milestone: | 2.4 → 2.5 |
|---|
comment:3 by , 12 years ago
It has occurred to me that this could be related to #1268 due to MgLayerCollection internally containing a MgNamedCollection instance.
comment:4 by , 12 years ago
| Owner: | set to |
|---|
comment:5 by , 12 years ago
Do you have sample code that caused this?
I strongly believe in this ticket's connection to #1268, but need some test code
comment:6 by , 12 years ago
| Milestone: | 2.5 → 2.6 |
|---|
comment:9 by , 2 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Assuming a clean slate from fresh SWIG .net bindings for MGOS 4.0
Is this still happening for 2.4?