I have ported it on android, but when I drag or zoom the map, It some times can crash. And I have found the reason: the parameter y that pass into this function makes the array (jumpTable8)[y][x] overstep the boundary. The status of parameter y when it crash of each map I list below: 1. Atlas: when y is 675 it crash, position is line 87 in StackTile.cpp "return (jumpTable8)[y][x];" 2. OpenStreetMap: y=256 line 89 return m_resultImage.color( (jumpTable8)[y][x] ); 3. Satellite View : y=675 line 92 4. Earth at Niget: y=675 line 92 5. Historical Map 1698: y=675 line 92 6. Precipitation(July): y=675 line 87 7. Precipitation(December): y=675 line 87 8. Temperature(December): y=675 line 87 9. Temperature(July): y=675 line 87 so, my question is: how can y be pass a 256 or 675 while the image height is 256 or 675.
*** Bug 331102 has been marked as a duplicate of this bug. ***
Created attachment 111645 [details] New crash information added by DrKonqi marble (2.2.20 (2.3 development version)) using Qt 5.10.1 Crash with latest master (19dbd3f1a480b45bd78b8747b1fc2d3f9b20ec79) in Lambert-Azimuthal projection when panning the globe. The whole width of the globe was just visible, maybe 1-2 pixels black border toward the edges. -- Backtrace (Reduced): #6 0xb7c39d06 in Marble::StackedTile::pixel(int, int) const (this=0xa9f09f90, x=68, y=256) at /home/shentey/Projekte/marble/src/src/lib/marble/StackedTile.cpp:86 #7 0xb7c3a250 in Marble::StackedTile::pixelF(double, double) const (this=0xa9f09f90, x=68.208818656907894, y=256) at /home/shentey/Projekte/marble/src/src/lib/marble/StackedTile.cpp:242 #8 0xb7c2210b in Marble::ScanlineTextureMapperContext::pixelValueF(double, double, unsigned int*) (this=0xa2fdc158, lon=1.9893203963311861, lat=2.832897325737199e-17, scanLine=0xa504c110) at /home/shentey/Projekte/marble/src/src/lib/marble/ScanlineTextureMapperContext.cpp:75 #9 0xb7c27682 in Marble::GenericScanlineTextureMapper::RenderJob::run() (this=<optimized out>) at /home/shentey/Projekte/marble/src/src/lib/marble/GenericScanlineTextureMapper.cpp:254 #10 0xb5eb2a27 in () at /usr/lib/libQt5Core.so.5
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!