After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 592416 - Repeated file discoveries sometimes hang on cygwin
Repeated file discoveries sometimes hang on cygwin
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-python
0.10.22
Other Cygwin
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-20 06:20 UTC by Ionut Turturica
Modified: 2011-05-18 10:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Ionut Turturica 2009-08-20 06:20:48 UTC 
I noticed that sometimes I get this kind of error messages:

(gst-discover:2012): GStreamer-CRITICAL **: Bus bus1 has no signal watches attached

More importantly sometimes python hangs while discovering media files through gst-python binding. I've seen it only on Cygwin (1.5 and 1.7), linux builds dont have this issue.

Unpack gst-python-0.10.16 and run gstfile.py from examples directory:

gstfile.py /path/to/some/media/files/*.avi
Comment 1 Sebastian Dröge (slomo) 2009-08-30 20:01:13 UTC 
Could you try to get backtraces from the CRITICAL above (set G_DEBUG=fatal_warnings to get a SIGABRT on warnings/criticals)? Also for the hanging python backtraces would be nice to have of all threads.
Comment 2 Ionut Turturica 2009-08-30 20:57:09 UTC 
This is what I got in the python.exe.stackdump:

Exception: STATUS_ACCESS_VIOLATION at eip=19138C6C
eax=00A9E9C0 ebx=00AA7DF8 ecx=00000100 edx=00A9E5C0 esi=FFFFFC00 edi=00AA81F8
ebp=19B7C8D8 esp=19B7C820 program=D:\cygwin-2\bin\python.exe, pid 6084, thread unknown (0x12F4)
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
19B7C8D8  19138C6C  (00C19240, 00AA7DF8, 19B7C9C4, 00BDB910)
19B7C9D8  190DCCFE  (00000300, 00000000, 00000000, 01E84800)
19B7CB38  1905F658  (00000300, 19B7CBA8, 00000000, 00000000)
19B7CBC8  1906336E  (00FCCB00, 00B0D308, 19B7CC18, 629440EF)
19B7CC18  629766FE  (00A3AC40, 006FBED8, 19B7CC38, 00C4B8D8)
19B7CC58  62976EC7  (00FCCA40, 00B0D308, 00000000, 6AA7E6D8)
19B7CCD8  61912F91  (00FCCA40, 006C5D40, 19B7CD18, 6AA42732)
19B7CD18  62992903  (00B0F4F0, 006C5F68, 00000000, 00000000)
19B7CD58  6AA8959A  (006C5FF8, 009BDE28, 00000000, 009BDEB0)
19B7CD78  6AA87909  (009BDE28, FFFFFFFF, 611688E0, 610040DA)
19B7CDB8  610B0A7B  (009BDE58, 19B7CDF0, 610B0A00, 19B7CDF0)
610B0A00  61004416  (8908758B, 5E8D2434, D82AE858, 7B83FFFF)
     14 [unknown (0x12F4)] python 6084 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
Comment 3 André Klapper 2009-08-31 17:12:13 UTC 
Reopening as per last comment.
Removing self-set gnome-target. Please don't do this.
Comment 4 Edward Hervey 2011-05-16 18:56:41 UTC 
any chance you could get a useful backtrace (with like function names and argument values) ?
Comment 5 Ionut Turturica 2011-05-18 05:56:32 UTC 
No, not really. That's an abandoned project. Sorry.