Could you attach a minimal testcase, please? In addition, type about:crashes in location bar and post some crash IDs (bp-...). Does it happen with a fresh profile? https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles (don't import anything)
This looks the same as bug 740325.
yes it is, now i see this byself inside the log "Firefox 17.0.1 Crash Report [@ _VEC_memcpy | _cairo_surface_snapshot_copy_on_write ]"
bug can be set on confirmed needs fix (memory leak in firefox?) ;)
mmhhh maybe we have different OS or something, my Problem isn't a single Problem lot of user have the same, see previous messages
It does not matter how many people have the problem. If you can provide a simple set of steps with a simple example page to reproduce the issue, the likelihood a developer will be able to fix the issue is much greater.
sure but in the description i have explained more i can't do... maybe it's an OS or special Hardware Bug or something, most programmers work on linux and windoof is in most case the biggest bug ;)
windoof means windows ;)
Could you paste the section "graphics" from about:support please. In addition, could you try with hardware acceleration disabled (Options > Advanced > General, restart FF17). Does it crash with HWA off too?
no without activated hardware accrelation it don't occur or maybe only currently not. I'm not really sure what's the reason for the problem...
i think it's an foolish hardware acceleration bug. Please see additional this https://bugzilla.mozilla.org/buglist.cgi?quicksearch=_VEC_memcpy Testcase for all which have this Problem Try follow: disable hardware acceleration (Options > Advanced > General, restart Do crash now too? Then enable hardware acceleration again (don't forget to restart) Do it crash now again? For me is this really the one and only solution to disable hardware acceleration - no crash while printing since this change in settings. It will be great if more user can check this so that a developer can fix this bug, this occur since FF/TB 15 if i have see this right! Crash Reason EXCEPTION_ACCESS_VIOLATION_READ sounds not nice!
(In reply to Bill Gianopoulos [:WG9s] from comment #3) > This looks the same as bug 740325. It's indeed a dupe.