|
|
#1 | |
|
Registered User
Join Date: Oct 2005
Posts: 14
|
Visiting this web page in either Firefox or a different, WebKit-based browser causes X to freeze at 100% CPU:
http://www.fountainpennetwork.com/fo...erlord-orange/ The first time I went to the page, the second sample image in the first post was a weird jumble of areas of the screen that were or had recently been visible. When I opened the image in a tab, X froze. The cursor was sometimes still movable. I rebooted and went to the page in Firefox again, and it froze X without opening the image separately. I rebooted and opened the page in the WebKit browser, and X froze again. I think the image in question is this one, the second: http://i1248.photobucket.com/albums/...servations.jpg But I'm not completely sure if it's that one or the third one. It's hard for me to test since it causes the crash. I visited the page in Firefox on another computer with an AMD chipset using the open-source drivers, and there was no crash. The Xorg.log file showed this after X froze: Code:
[ 428.025] (EE) NVIDIA(0): Failed to allocate 2D engine [ 428.025] (EE) NVIDIA(0): *** Aborting *** [ 428.025] (EE) NVIDIA(0): Failed to allocate 2D objects [ 428.025] (EE) NVIDIA(0): *** Aborting *** [ 428.025] (EE) NVIDIA(0): Error recovery failed. [ 428.025] (EE) NVIDIA(0): *** Aborting *** [ 436.027] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00000000, 0x0000002c) [ 443.027] (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00000000, 0x0000002c) [ 451.086] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00000000, 0x00001c88) [ 458.086] (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00000000, 0x00001c88) [ 461.088] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00000000, 0x00002560) [ 468.088] (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00000000, 0x00002560) |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Oct 2005
Posts: 14
|
I just found another one that causes it: http://www.fountainpennetwork.com/fo...tralian-roses/ The third or fourth JPEG in the first post, which is 2047x700-something pixels is the problem. When I first scrolled down to it, the entire screen flickered one time, and the resized display of the JPEG in that tab was a jumble of other screen areas, but everything was otherwise ok. I changed to another tab in Firefox. When I changed back to the first tab, X froze.
I was able to SAK the X server several times, and I restarted X several times, but X would never work properly again: lightdm only displayed a mostly-black screen with square patches of white static. I even removed the nvidia module and reloaded it, but that didn't help. I had to reboot the entire system. This is very strange, because apparently this image comes from the same forum user. What could he be doing so different with his JPEGs? I'm wondering if it's something to do with the dimensions of the image (wide and short, and 2047 is very close to the "magic number" of 2048), yet I can display much larger photos than that without a problem. Also, these messages appeared in the ring buffer: Code:
Nov 4 05:05:45 kernel: [138058.950126] NVRM: Xid (0000:01:00): 6, PE0001 Nov 4 05:06:43 kernel: [138116.675426] NVRM: Xid (0000:01:00): 6, PE0001 |
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Oct 2005
Posts: 14
|
And here's another one, with images from the same person: http://www.fountainpennetwork.com/fo...8#entry2506408
|
|
|
|
![]() |
| Thread Tools | |
|
|