Summary: | >=www-client/chromium-bin-4.0.295.0_p35884 crashing while trying to upload file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Oschtan <dawnstyle> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | karl, koolfy, leon+gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | ht-wanted | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 333119 | ||
Bug Blocks: | |||
Attachments: | valgrind output |
Description
Oschtan
2010-02-01 10:32:18 UTC
Please, provide steps you've used to reproduce the crash. Also I'm unsure, but is it possible to get backtrace? For example, when trying to download any image on facebook.com. Immediately after selecting jpeg images chromium-bin collapses and restarting does not try to restore the session. Hmm. Maybe blame jpeg? Backtrace... Hmm. How to get backtrace chromium-bin for amd64? Where to get gdb32? Without difficulty. same issue here. When you launch /usr/bin/chromium-bin in the console you see: The program 'exe' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 351 error_code 3 request_code 10 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Created attachment 221919 [details]
valgrind output
I tried to run chromium-bin through valgrind but it segfaulted before I could get to a upload page. Attached is valgrind output.
Are you able to reproduce with ~5.0.308.0_p37385? Are you able to reproduce with www-client/chromium? Which version(s) of media-libs/jpeg do you have installed? I have media-libs/jpeg-8 and chromium-bin-5.0.308.0_p37385 99% of websites work fine, the crash though is 100% reproducible on file upload. I'll try later with the latest chromium, it take me over an hour to compile it, which is the main reason I used chromium-bin. chromium is probably in one of the top 10 longest compile times for a single package. Your right about the jpeg issue. I was trying to upload a jpg and got this backtrace with gdb: Core was generated by `/opt/chromium.org/chrome-linux/chrome'. Program terminated with signal 11, Segmentation fault. #0 0xb6c7665f in jpeg_CreateDecompress (cinfo=0xa6036c8, version=80, structsize=484) at ./jdapimin.c:37 37 ./jdapimin.c: No such file or directory. in ./jdapimin.c (gdb) bt #0 0xb6c7665f in jpeg_CreateDecompress (cinfo=0xa6036c8, version=80, structsize=484) at ./jdapimin.c:37 #1 0xb033e247 in gdk_pixbuf__jpeg_image_begin_load (size_func=0xb7153bd0 <gdk_pixbuf_loader_size_func>, prepared_func=0xb7153fe0 <gdk_pixbuf_loader_prepare>, updated_func=0xb7153f10 <gdk_pixbuf_loader_update>, user_data=0xa5dfc60, error=0x0) at io-jpeg.c:660 #2 0xb7153df5 in gdk_pixbuf_loader_load_module (loader=0xa5dfc60, image_type=<value optimized out>, error=0x0) at gdk-pixbuf-loader.c:382 #3 0xb7154a0f in gdk_pixbuf_loader_eat_header_write (loader=0xa5dfc60, buf=0xbf807560 "ÿØÿà", count=41648, error=0x0) at gdk-pixbuf-loader.c:417 #4 IA__gdk_pixbuf_loader_write (loader=0xa5dfc60, buf=0xbf807560 "ÿØÿà", count=41648, error=0x0) at gdk-pixbuf-loader.c:463 #5 0xb715222b in IA__gdk_pixbuf_new_from_file_at_scale (filename=0xa639c70 "/home/karl/Desktop/karl.jpg", width=256, height=512, preserve_aspect_ratio=1, error=0x0) at gdk-pixbuf-io.c:1248 #6 0xb715251e in IA__gdk_pixbuf_new_from_file_at_size (filename=0xa639c70 "/home/karl/Desktop/karl.jpg", width=256, height=512, error=0x0) at gdk-pixbuf-io.c:1090 #7 0x080f523c in SelectFileDialogImpl::OnUpdatePreview(_GtkFileChooser*, SelectFileDialogImpl*) () #8 0xb705ba94 in IA__g_cclosure_marshal_VOID__VOID (closure=0xa2f1830, return_value=0x0, n_param_values=1, param_values=0xaa99b908, invocation_hint=0xbf81774c, marshal_data=0x80f51fc) at gmarshal.c:77 #9 0xb704df52 in IA__g_closure_invoke (closure=0xa2f1830, return_value=0x0, n_param_values=1, param_values=0xaa99b908, invocation_hint=0xbf81774c) at gclosure.c:767 #10 0xb706442d in signal_emit_unlocked_R (node=0xa39cb70, detail=0, instance=0xa42f048, emission_return=0x0, instance_and_params=0xaa99b908) at gsignal.c:3247 #11 0xb7065aaf in IA__g_signal_emit_valist (instance=0xa42f048, signal_id=206, detail=0, var_args=0xbf817928 "Xy\201¿<Ç\004·Yì.·ôï\a·Xy\201¿\224º\005·\200{1\nHðB\n\233Æ\004·ôï\a·\020º\005·P\027_\nèy\201¿Rß\004·P\027_\n") at gsignal.c:2980 #12 0xb7065da5 in IA__g_signal_emit_by_name (instance=0xa42f048, detailed_signal=0xb74ee27c "update-preview") at gsignal.c:3074 #13 0xb72eec78 in delegate_update_preview (chooser=0xa317b80, data=0xa42f048) at gtkfilechooserutils.c:344 #14 0xb705ba94 in IA__g_cclosure_marshal_VOID__VOID (closure=0xa5f1750, return_value=0x0, n_param_values=1, param_values=0xaea93290, invocation_hint=0xbf817abc, marshal_data=0xb72eec50) at gmarshal.c:77 #15 0xb704df52 in IA__g_closure_invoke (closure=0xa5f1750, return_value=0x0, n_param_values=1, param_values=0xaea93290, invocation_hint=0xbf817abc) at gclosure.c:767 #16 0xb706442d in signal_emit_unlocked_R (node=0xa39cb70, detail=0, instance=0xa317b80, emission_return=0x0, instance_and_params=0xaea93290) at gsignal.c:3247 #17 0xb7065aaf in IA__g_signal_emit_valist (instance=0xa317b80, signal_id=206, detail=0, var_args=0xbf817c98 "È|\201¿<Ç\004·Yì.·ôï\a·È|\201¿\224º\005·\b\020D\n\200{1\n\233Æ\004·ôï\a·\020º\005·\230\025_\nX}\201¿Rß\004·\230\025_\n") at gsignal.c:2980 #18 0xb7065da5 in IA__g_signal_emit_by_name (instance=0xa317b80, detailed_signal=0xb74ee27c "update-preview") at gsignal.c:3074 #19 0xb72eec78 in delegate_update_preview (chooser=0xa441008, data=0xa317b80) at gtkfilechooserutils.c:344 #20 0xb705ba94 in IA__g_cclosure_marshal_VOID__VOID (closure=0xa5f1598, return_value=0x0, n_param_values=1, param_values=0xa3940c8, invocation_hint=0xbf817e2c, marshal_data=0xb72eec50) at gmarshal.c:77 #21 0xb704df52 in IA__g_closure_invoke (closure=0xa5f1598, return_value=0x0, n_param_values=1, param_values=0xa3940c8, invocation_hint=0xbf817e2c) at gclosure.c:767 #22 0xb706442d in signal_emit_unlocked_R (node=0xa39cb70, detail=0, instance=0xa441008, emission_return=0x0, instance_and_params=0xa3940c8) at gsignal.c:3247 #23 0xb7065aaf in IA__g_signal_emit_valist (instance=0xa441008, signal_id=206, detail=0, var_args=0xbf818008 "0\200\201¿\rö+·\020°_\n\222\004") at gsignal.c:2980 #24 0xb7065da5 in IA__g_signal_emit_by_name (instance=0xa441008, detailed_signal=0xb74ee27c "update-preview") at gsignal.c:3074 #25 0xb72dd900 in check_preview_change (impl=0xa441008) at gtkfilechooserdefault.c:10408 #26 0xb72e60d7 in list_selection_changed (selection=0xa5ec380, impl=0xa441008) at gtkfilechooserdefault.c:10801 #27 0xb705ba94 in IA__g_cclosure_marshal_VOID__VOID (closure=0xa3328d0, return_value=0x0, n_param_values=1, param_values=0xad561160, invocation_hint=0xbf81824c, marshal_data=0xb72e6060) at gmarshal.c:77 #28 0xb704df52 in IA__g_closure_invoke (closure=0xa3328d0, return_value=0x0, n_param_values=1, param_values=0xad561160, invocation_hint=0xbf81824c) I have both media-libs/jpeg-8 and media-libs/jpeg-6b-r9 Just confirmed that www-client/chromium-5.0.307.11 jpg upload works fine.
Perhaps the problem is that the libjpeg it's compiled with doest not match properly the gentoo media-libs/jpeg
No matter how many times I do emerge @preserved-rebuild
I still see the message:
>>> package: media-libs/jpeg-8
* - /usr/lib/libjpeg.so.62
* used by /opt/chromium.org/chrome-linux/chrome (www-client/chromium-bin-5.0.308.0_p37385)
* used by /opt/savage/silverback.bin (games-strategy/savage-bin-2.00e)
* used by /opt/vmware/server/console/lib/libconf/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-jpeg.so (app-emulation/vmware-server-console-1.0.9.156507)
Use
Please post output of the following commands: ldd /opt/chromium.org/chrome-linux/chrome equery files jpeg | grep .so. Does "emerge -1av media-libs/jpeg:62" solve the problem? $ ldd /opt/chromium.org/chrome-linux/chrome /opt/chromium.org/chrome-linux/chrome: /lib/libz.so.1: no version information available (required by /opt/chromium.org/chrome-linux/chrome) linux-gate.so.1 => (0xb7837000) libX11.so.6 => /usr/lib/libX11.so.6 (0xb76f7000) libdl.so.2 => /lib/libdl.so.2 (0xb76f3000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb76e9000) libXss.so.1 => /usr/lib/libXss.so.1 (0xb76e5000) libXext.so.6 => /usr/lib/libXext.so.6 (0xb76d5000) librt.so.1 => /lib/librt.so.1 (0xb76cc000) libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb732a000) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb729e000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb7283000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7269000) libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb725d000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7218000) libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb71a2000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7165000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7160000) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb715a000) libnspr4.so.0d => not found libpthread.so.0 => /lib/libpthread.so.0 (0xb7065000) libz.so.1 => /lib/libz.so.1 (0xb7053000) libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0xb701f000) libm.so.6 => /lib/libm.so.6 (0xb6ff9000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb6fcd000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb6f44000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb6f22000) libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb6efc000) libasound.so.2 => /usr/lib/libasound.so.2 (0xb6e40000) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb6e2f000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb6e07000) libstdc++.so.6 => /usr/lib/gcc/i686-pc-linux-gnu/4.3.4/libstdc++.so.6 (0xb6d19000) libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/4.3.4/libgcc_s.so.1 (0xb6d0b000) libc.so.6 => /lib/libc.so.6 (0xb6bba000) /lib/ld-linux.so.2 (0xb7838000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb6b9f000) libXau.so.6 => /usr/lib/libXau.so.6 (0xb6b9a000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb6b94000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb6b90000) libXi.so.6 => /usr/lib/libXi.so.6 (0xb6b86000) libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb6b7d000) libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb6b71000) libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xb6b6d000) libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xb6b69000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb6b63000) libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb6b01000) libxcb-render-util.so.0 => /usr/lib/libxcb-render-util.so.0 (0xb6afb000) libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0xb6af2000) libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0xb6a87000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb6a5e000) libORBit-2.so.0 => /usr/lib/libORBit-2.so.0 (0xb6a07000) libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0xb69ea000) libnsl.so.1 => /lib/libnsl.so.1 (0xb69d2000) libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xb699a000) $ equery files jpeg | grep .so. /usr/lib/debug/usr/lib/libjpeg.so.62.debug /usr/lib/libjpeg.so.62 /usr/lib/debug/usr/lib/libjpeg.so.8.0.0.debug /usr/lib/libjpeg.so.7 /usr/lib/libjpeg.so.8 /usr/lib/libjpeg.so.8.0.0 media-libs/jpeg:62 is emerged and does not solve the problem. They have lots of issues on upload+crash subject http://code.google.com/p/chromium/issues/list?can=2&q=upload+crash&sort=-id&colspec=ID+Stars+Pri+Area+Feature+Type+Status+Summary+Modified+Owner+Mstone+OS&x=mstone&y=area&cells=tiles I'd appreciate a report how this works in chromium-bin-5.0.375.127. This should be fixed now for all chromium-bin versions in the tree. |