Description of problem: Application crashes when resizing window or during panning. Sometimes I can use application serveral minutes, but often the crash happens during first time I use panning/resizing. There was Mapnik map layer and several GPS tracks visible when crash occurred. Version-Release number of selected component: viking-1.6-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/viking crash_function: strncmp executable: /usr/bin/viking global_pid: 22351 kernel: 4.0.4-303.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Sat 2013-07-06 18:33:51 EEST, end at Sun 2015-06-21 23:30:37 EEST. -- Truncated backtrace: Thread no. 1 (6 frames) #0 strncmp at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:164 #1 flush_matching at mapcache.c:224 #2 a_mapcache_remove_all_shrinkfactors at mapcache.c:257 #3 map_download_thread at vikmapslayer.c:1638 #4 thread_helper at background.c:136 #6 g_thread_proxy at gthread.c:764 Potential duplicate: bug 1229082
Created attachment 1041508 [details] File: backtrace
Created attachment 1041509 [details] File: cgroup
Created attachment 1041510 [details] File: core_backtrace
Created attachment 1041511 [details] File: dso_list
Created attachment 1041512 [details] File: environ
Created attachment 1041513 [details] File: limits
Created attachment 1041514 [details] File: maps
Created attachment 1041515 [details] File: mountinfo
Created attachment 1041516 [details] File: namespaces
Created attachment 1041517 [details] File: open_fds
Created attachment 1041518 [details] File: proc_pid_status
It seems that I have the same problem. Has there been any progress?
(In reply to Peter F. Patel-Schneider from comment #12) > It seems that I have the same problem. > > Has there been any progress? I'm not sure if this is the same issue that I have, but it sounds somewhat similar: http://sourceforge.net/p/viking/bugs/121/ However, I haven't tried the patched version yet, so I cannot confirm if this bug is now fixed.
*** This bug has been marked as a duplicate of bug 1229082 ***