|
POST
|
Good Day My apologizes, I was exceedingly unclear. When I mentioned I saw the memory climb, I was talking about the system monitor on my OS, the first screenshots are taken using the development repo, then I switched to our production version to get a much bigger network loaded. The first picture is sitting on the dashboard before loading a map: After loading 1 map and going back to the dashboard; After cycling that 5 more times, so I've loaded the map 6 times, and I'm back at the dashboard, this is after forced garbage collection: Specifically I'm referencing Brave, although I'll see the same activity from any Chromium based browser. Oddly enough Firefox is stable and doesn't throw the memory around, When I view the heap through the memory tab in the console, that's staying stable, it's the system memory that seems to be all over the board. If I run this same kind of test on our production version using the following network, which is 7000+ segments 45 Feature Layers, 10 of them having meaningful data : Then I cycle through ~20 maps, and land back at the dashboard, after a forced garbage collection I'm setting at: To be fair, this is much better then it was in 4.16, where that number would commonly go over 2 GiB+, but it seems something is still kicking around. I've been sitting at the Dashboard for ~10+ minutes and that number is fairly stable. Thanks
... View more
10-21-2020
12:06 PM
|
0
|
1
|
2682
|
|
POST
|
Good Day Sorry for the delay in reply, I integrated your suggestions and added a much bigger data file. This code is roughly laid out to match our production code: esri-printtask-issue/src/app at master · docmur/esri-printtask-issue · GitHub I'm still seeing the memory climb when I switch back and forth, is there anything else you can recommend? Thanks
... View more
10-20-2020
02:18 PM
|
0
|
0
|
2682
|
|
POST
|
Hey This would be a continuation, but to prevent from it getting bunched together I made this a new task. To be fair the only change on this test repo is that I changed the version to 4.17 from next. If we need to wait until December that's fine. We'll wait for a fix, I just wanted to make sure this was known, feel free to use that code I posted for testing. Thanks
... View more
10-13-2020
11:20 AM
|
0
|
1
|
2682
|
|
POST
|
Good Day I'm trying out 4.17 with the following test repo: GitHub - docmur/angular-esri-memory-test, I added in the new view.destroy and map.destroy but the memory is still not getting freed! Have I taken the correct steps to free the memory? Thanks
... View more
10-13-2020
08:49 AM
|
0
|
8
|
2807
|
|
POST
|
That's my thinking, so if I don't run into any issue tomorrow with it then we'll mark is "solved", because if it's not causing a problem then I can wait.
... View more
09-24-2020
01:34 PM
|
0
|
0
|
1849
|
|
POST
|
I tested out 4.15 and it seems to be working perfectly fine, so I'm not sure why that is but I haven't had a problem all day with it. I see a lot of errors but they're not breaking anything so that's good enough to bridge until 4.17
... View more
09-24-2020
12:32 PM
|
0
|
2
|
1849
|
|
POST
|
Good Day Wondering why I keep errors on the Home / Print Task Widget? Both give me: My test code: GitHub - docmur/esri-printtask-issue Thanks
... View more
09-24-2020
10:46 AM
|
0
|
0
|
669
|
|
POST
|
Sweet! Is there a way to get this pushed on to 4.16?
... View more
09-23-2020
03:02 PM
|
0
|
4
|
1849
|
|
POST
|
I ran the code on /next and it looks like the problem is "solved", I'm seeing a lot of errors but nothing is doing an inf loop:
... View more
09-23-2020
12:29 PM
|
0
|
8
|
2790
|
|
POST
|
Yes: It seems to have something to do with stacking the data. I've disabled the indexDB functionality so we have to load from a HTTP endpoint but I can still run into it.
... View more
09-23-2020
12:16 PM
|
0
|
0
|
2790
|
|
POST
|
We've seen this problem across Firefox / Chromium browsers and on Windows / Linux. I'm currently on Ubuntu 20.04 Brave.
... View more
09-23-2020
11:48 AM
|
0
|
11
|
2790
|
|
POST
|
Okay, I'll send the HAR file and I'll test on /next to see if I can cause the same problem. In the case I run into the error it's just from loading the Feature Layer, I'll see one of the port closed errors and then run into this: [esri.views.layers.2d.features.support.AttributeStore] e {name: "mapview-attribute-store", message: "Encountered an error during client initialization", details: e} details: e details: undefined dojoType: "cancel" message: "Abort job: worker closing" name: "AbortError" message: "Encountered an error during client initialization" name: "mapview-attribute-store" Which happens to then cause and info loop, which requires me to jump away from the map quickly, to prevent a total lock up.
... View more
09-23-2020
11:46 AM
|
0
|
0
|
2790
|
|
POST
|
Yes, that's very likely for our use case, as we store the data in the the browser and fetch it from IndexDB when we need it. Is there a way I can listen for the connect to be ready / set before I go to create the feature layer?
... View more
09-23-2020
10:16 AM
|
0
|
1
|
2436
|
|
POST
|
How can I upload a file or is there any email I can send the HAR file to?
... View more
09-23-2020
10:14 AM
|
0
|
14
|
2790
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 04-25-2025 07:33 AM | |
| 1 | 03-18-2025 11:15 AM | |
| 1 | 10-07-2022 08:14 AM | |
| 1 | 08-25-2023 10:47 AM | |
| 1 | 02-23-2023 08:22 AM |
| Online Status |
Offline
|
| Date Last Visited |
10-24-2025
07:12 AM
|