Fixed
Status Update
No update yet.
Comments
zm...@gmail.com
Oh and one more thing I forgot. Fragment A's child fragment is also part of the nested navigation controller, for which the Fragment A contains the root NavHostFragment, and not the root nav controller Fragment A is part of. So maybe it's not due to FragmentManager, maybe it's the nested navigation controller prematurely removing it's own fragment, when exitAnimation starts for it's root/parent fragment A.
Other than that, instanceState of the child fragment is preserved properly when navigating back and forth.. It's just that it's view is removed prematurely for some reason.
Other than that, instanceState of the child fragment is preserved properly when navigating back and forth.. It's just that it's view is removed prematurely for some reason.
cb...@google.com
Can you attach a sample project that reproduces your issue?
Description
1. Add at least two markers that are far apart from each other (for example, one in the US and one in Australia).
2. Use a custom icon with custom scaling for those two markers (using the scaledSize parameter of MarkerImage).
3. Set the zoom level to 15 or closer.
4. Load this map in Chrome on OS X.
The map will take too long to load, and may crash. If it does load eventually, zooming in to a marker will cause it to crash. Sometimes panning the map around will also cause a crash or very poor performance.
This bug appeared in the last week or two, and does not appear in 3.4.
Sample code:
Version 3.5 (latest stable) showing the bug:
Same code with 3.4 (no bug, works fine):
System info:
Macbook Air, 1.4ghz Core 2 Duo, 4GB RAM
Mac OS X 10.6.6 (also tested on Lion, same issue)
Chrome 13.0.782.112
Thanks,
Allan, concept3D Inc.