reopen 314411 thanks On 12/29/07, Debian Bug Tracking System <[EMAIL PROTECTED]> wrote: > This is an automatic notification regarding your Bug report > which was filed against the xine-ui package: > > #314411: xine-ui: aaxine with sound crashes when maximized > > It has been closed by Reinhard Tartler <[EMAIL PROTECTED]>.
Will you stop closing this bug without asking me if it's fixed, please? I can still reproduce this. It's intermittent whether it happens the first time I maximize the window or the first time I restore the maximized window to an unmaximized state after that, but it happened in one of those situations 5 times out of my 5 tests. Running valgrind on aaxine gives me this: AFD changed from -2 to -1 ==16382== ==16382== Invalid free() / delete / delete[] ==16382== at 0x402465C: free (vg_replace_malloc.c:323) ==16382== by 0x4090202: X_flush (aax.c:350) ==16382== by 0x4091A23: __aa_X_getsize (aax.c:290) ==16382== by 0x4091DC4: X_getchar (aaxkbd.c:86) ==16382== by 0x4094672: aa_getevent (aain.c:57) ==16382== by 0x804A3A2: aaxine_get_key_event (in /usr/bin/aaxine) ==16382== by 0x804AE61: main (in /usr/bin/aaxine) ==16382== Address 0x9cac318 is 0 bytes inside a block of size 204,800 free'd ==16382== at 0x402465C: free (vg_replace_malloc.c:323) ==16382== by 0x4090202: X_flush (aax.c:350) ==16382== by 0x4093729: aa_flush (aaflush.c:71) ==16382== by 0x4B1FB34: aa_display_frame (video_out_aa.c:231) ==16382== ==16382== ---- Attach to debugger ? --- [Return/N/n/Y/y/C/c] ---- It looks to me like this happens because X_flush() is ultimately being called from multiple threads simultaneously (main.c:582's call to aa_getevent() and video_out_aa.c:231's call to aa_flush()). Checking briefly, I didn't find anything in the aalib docs about thread safety; in the absence of assurances (and in the presence of a demonstrated problem :-) I would be inclined to say that aalib is not thread safe, and so calls to aalib functions need to be protected by a mutex. That's all speculation based on brief investigation, of course. This problem could be unrelated to the crash, or I could be wrong about the source of this problem. The theory that it's a race condition would help to explain why I can reproduce this on my system but you can't on yours, though. Cheers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
