Problem scanning huge source (mem leak)?
#90
(2017-03-05, 18:04)DaveBlake Wrote: How about the memory leak with Library Data Provider running?

Not looking that good ;(

This is Milhouse running since yesterday evening.
LDP & skin.widget together with Xonfluence (tricked it into with adapting xbmc.gui version from required 5.12 to 5.13).
This was running over night and produced 9 crashlogs and at minimum 1 reboot Confused

Code:
# grep -C6 "Thread debugging using libthread_db enabled" kodi_crash*

kodi_crash.log:[Thread debugging using libthread_db enabled]
kodi_crash.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crash.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crash.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crash.log-#0  0x76f98b64 in memcmp () from /usr/lib/libarmmem.so
kodi_crash.log-[Current thread is 1 (Thread 0x74f2a000 (LWP 2304))]
kodi_crash.log-
--

kodi_crashlog_20170305224525.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170305224525.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170305224525.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170305224525.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170305224525.log-#0  0x008daf48 in CMusicDatabase::SetMusicTagScanVersion(int) ()
kodi_crashlog_20170305224525.log-[Current thread is 1 (Thread 0x74f10000 (LWP 453))]
kodi_crashlog_20170305224525.log-
--

kodi_crashlog_20170306002511.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306002511.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306002511.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306002511.log-Program terminated with signal SIGABRT, Aborted.
kodi_crashlog_20170306002511.log-#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
kodi_crashlog_20170306002511.log-[Current thread is 1 (Thread 0x74ecf000 (LWP 629))]
kodi_crashlog_20170306002511.log-
--

kodi_crashlog_20170306004312.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306004312.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306004312.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306004312.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306004312.log-#0  malloc_consolidate (av=av@entry=0x73c00010) at malloc.c:4204
kodi_crashlog_20170306004312.log-[Current thread is 1 (Thread 0x512ff3a0 (LWP 1016))]
kodi_crashlog_20170306004312.log-
--

kodi_crashlog_20170306021431.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306021431.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306021431.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306021431.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306021431.log-#0  0x698ac684 in ?? ()
kodi_crashlog_20170306021431.log-[Current thread is 1 (Thread 0x66dff3a0 (LWP 1122))]
kodi_crashlog_20170306021431.log-
--

kodi_crashlog_20170306022337.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306022337.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306022337.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306022337.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306022337.log-#0  0x76f7cb64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306022337.log-[Current thread is 1 (Thread 0x74f0e000 (LWP 1334))]
kodi_crashlog_20170306022337.log-
--

kodi_crashlog_20170306034739.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306034739.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306034739.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306034739.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306034739.log-#0  0x76ee8b64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306034739.log-[Current thread is 1 (Thread 0x74e7a000 (LWP 1494))]
kodi_crashlog_20170306034739.log-
--

kodi_crashlog_20170306043401.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306043401.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306043401.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306043401.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306043401.log-#0  0x76f4bb64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306043401.log-[Current thread is 1 (Thread 0x74edd000 (LWP 1733))]
kodi_crashlog_20170306043401.log-
--

kodi_crashlog_20170306073316.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306073316.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306073316.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306073316.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306073316.log-#0  0x76f3cb64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306073316.log-[Current thread is 1 (Thread 0x74ece000 (LWP 1931))]
kodi_crashlog_20170306073316.log-
--

kodi_crashlog_20170306073949.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306073949.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306073949.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306073949.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306073949.log-#0  0x76f98b64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306073949.log-[Current thread is 1 (Thread 0x74f2a000 (LWP 2304))]
kodi_crashlog_20170306073949.log-

Only difference seems to be that memory isn't filling up that fast as you can see from the timestamps.
Reply


Messages In This Thread
RE: Problem scanning source - by DaveBlake - 2017-02-12, 13:00
RE: Problem scanning source - by Uatschitchun - 2017-02-12, 21:51
RE: Problem scanning huge source (mem leak)? - by Uatschitchun - 2017-03-06, 09:09
Logout Mark Read Team Forum Stats Members Help
Problem scanning huge source (mem leak)?0