-
Notifications
You must be signed in to change notification settings - Fork 444
#11779: FIX Setting the map projection freezes MapStore causing OOM if resolutions configured in new.json file with a different projection #11788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mahmoudadel54 what about old maps having the old configuration? Probably we should at least automatically update the map state at loading time so that the new logic is applied and when the map is saved the new configuration is also persisted. All in a transparent and automated way ensuring also a good backward compatibility. What do you think @MV88? Up to you to review.
MV88
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mahmoudadel54 not much to say, but one thing to be sure
What about #11788 (review) @MV88? |
MV88
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…e if resolutions configured in new.json file with a different projection Description: - prevent OOM by enforcing projection-aware resolutions in new.json file in mapOptions.view - Add strict check: only use configured resolutions if `view.projection` matches target SRS - Eliminates infinite tile loading and out-of-memory crashes when switching to different CRS - fix print file by passing the projection prop with resolutions to gurantee the above check - add unit test
…e if resolutions configured in new.json file with a different projection Description: - edit unit test uses resolutions without projection
a8ab8f3 to
49b10c7
Compare
…f resolutions configured in new.json file with a different projection (#11788) * #11779: FIX Setting the map projection crashes MapStore if resolutions configured in new.json file with a different projection Description: - prevent OOM by enforcing projection-aware resolutions in new.json file in mapOptions.view - Add strict check: only use configured resolutions if `view.projection` matches target SRS - Eliminates infinite tile loading and out-of-memory crashes when switching to different CRS - fix print file by passing the projection prop with resolutions to gurantee the above check - add unit test * #11779: FIX Setting the map projection crashes MapStore if resolutions configured in new.json file with a different projection Description: - edit unit test uses resolutions without projection * - resolve review comments by editing the order of viewOptions in openlayers/Map.js (cherry picked from commit 4e68715)
|
Successfully created backport PR for |
|
@ElenaGallo waiting for you for before merging the backport |
@MV88 I saw you have merged, but can I have an answer to this please? |
|
Test passed, @tdipisa backport can be merged |
we have noticed that current implementation might require an additional effort in order to cover all cases, see here #11779 (comment) i'll revert this |
… MapStore causing OOM if resolutions configured in new.json file with a different projection (geosolutions-it#11788)" This reverts commit 4e68715.
…e causing OOM if resolutions configured in new.json file with a different projection (geosolutions-it#11788) * geosolutions-it#11779: FIX Setting the map projection crashes MapStore if resolutions configured in new.json file with a different projection Description: - prevent OOM by enforcing projection-aware resolutions in new.json file in mapOptions.view - Add strict check: only use configured resolutions if `view.projection` matches target SRS - Eliminates infinite tile loading and out-of-memory crashes when switching to different CRS - fix print file by passing the projection prop with resolutions to gurantee the above check - add unit test * geosolutions-it#11779: FIX Setting the map projection crashes MapStore if resolutions configured in new.json file with a different projection Description: - edit unit test uses resolutions without projection * - resolve review comments by editing the order of viewOptions in openlayers/Map.js
… MapStore causing OOM if resolutions configured in new.json file with a different projection (geosolutions-it#11788)" (geosolutions-it#11821) This reverts commit 4e68715.
Description
This PR includes:
view.projectionin new.json file matches target SRS in createView** the new edits includes -> a projection should be added to resolutions/scales in mapOptions.view in new.json file to be read properly. **
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#11779
What is the new behavior?
The OOM behavior not happen now if a resolutions and projection provided in new.json file and user switch to different projection rather than the resolutions one.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information
This new.json for test
I think guides should be added for this edit