On Fri, Feb 16, 2007 at 03:09:43PM +0000, Dave Howorth wrote: > Russell Jones wrote: > > Call me a numerologist mystic if you like, but I suspect the height > > being >32767 pixels (the limit of a signed 16-bit integer) has something > > to do with it. What happens if it's resized to less than this? What if > > it's just saved with the same size by e.g. gimp? > > Call me a sucker if you like but I tried this. I'd been wondering the > same thing :) It's fascinating. > > When I resized it to 32768 pixels high, I got the same error message. > When I resized it to 32767 pixels high, firefox crashed: > > The program 'Gecko' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadAlloc (insufficient resources for operation)'. > (Details: serial 23489 error_code 11 request_code 53 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.) > > Perhaps that's useful info to add to Jan's bug report.
I seem to remember that X11 was limited to pixmaps of 32767 width and height at some point in time. Likely Firefox tries to create a larger one instead of rescaling before creation. Ciao, Marcus -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
