This seems to happens only in FreeBSD, I noticed it since v33, but still failed in 34 35 and now chromium-36.0.1985.143_1. This is reported in the mailing list but I never got a reply to it, wonder if there's any chance this will ever work on FreeBSD!
over to maintainer group
Still happens in 37 Building with Debug generates an huge and unusable chrome bin, this is all I could get from gdb Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 814406400 (LWP 101765/chrome)] 0x00000000033a2929 in ?? () (gdb) bt #0 0x00000000033a2929 in ?? () #1 0x00000000033a28f5 in ?? () #2 0x0000000002d9d6a3 in ?? () #3 0x0000000002d96ae2 in ?? () #4 0x0000000002d24d0b in ?? () #5 0x0000000002daabe7 in ?? () #6 0x0000000002da87bf in ?? () #7 0x0000000002dab195 in ?? () #8 0x0000000002db659a in ?? () #9 0x0000000002db5e0f in ?? () #10 0x00000000022976ce in ?? () #11 0x00000000009e7e7c in ?? () #12 0x00000000009e856c in ?? () #13 0x0000000000a1d57f in ?? () #14 0x0000000805a8647e in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0 #15 0x0000000805a86843 in g_main_context_pending () from /usr/local/lib/libglib-2.0.so.0 #16 0x0000000805a868d4 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0 #17 0x0000000000a1d3a2 in ?? () #18 0x00000000009f6f66 in ?? () #19 0x00000000006c27a0 in ?? () #20 0x00000000022a08d9 in ?? () #21 0x00000000022a2df2 in ?? () #22 0x000000000229cd9f in ?? () #23 0x00000000009bbf91 in ?? () #24 0x00000000009bb656 in ?? () #25 0x000000000043cb59 in ?? () #26 0x000000000043ca2f in ?? () #27 0x00000008051d9000 in ?? () #28 0x0000000000000000 in ?? ()
Any feedback on this? Debug builds create a huge chrome binary, tried this with the 3 last versions and 36. Is anyone with a working debug version willing to test this and output the result? Thanks
This is working fine now... Probably google changed something at there side too! Version 38.0.2125.104 (290379) (64-bit) Works (altough a 2 weeks ago it dind't crash but any videos I tried to send from Plex or youtube should crashed the extension but not the browser) But today it works and with the same version of the extention (Version 38.0.2125.104 (290379) (64-bit)) So the only explanation possible is a the update of the dongle it self!