Opened 5 weeks ago

Closed 4 weeks ago

#19298 closed bug (fixed)

KDL while using Falkon (panic assert failed)

Reported by: AlienSoldier Owned by: nobody
Priority: normal Milestone: R1/beta6
Component: System/Kernel Version: R1/beta5
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

KDL screen shot defiled too fast to catch the start of the message. I typed continue perhaps 6 times and then the system came back so i decided to launch Falkon one more time and crash it again in the same session. Seem it showed less line in the end so i was able to take a picture of the start of the message this time around (included in ticket). Can create it within 20 seconds of starting Falkon (may do it with other apps, i did not test that extensivelly as the system is unusable for me in this state).

I disabled virtual memory completely and it does not help the problem. I did not made upgrade to the system after that as i wanted to be sure that the cause of the problem was known and not have something magically fix itself.

32 bit version and started with december 16 hrev58412. System work fine if i revert to my previous update december 7 hrev58388.

Attachments (2)

DSC00286.JPG (3.1 MB ) - added by AlienSoldier 5 weeks ago.
KDL screen picture
DSC00287.JPG (3.0 MB ) - added by AlienSoldier 4 weeks ago.

Change History (6)

by AlienSoldier, 5 weeks ago

Attachment: DSC00286.JPG added

KDL screen picture

comment:1 by waddlesplash, 5 weeks ago

Component: - GeneralSystem/Kernel

comment:2 by waddlesplash, 5 weeks ago

Please retest after hrev58425.

comment:3 by AlienSoldier, 4 weeks ago

Seem fine so far, hrev was already at 58429 when i made the upgrade. I got one KDL, one peculiar i never got before. Probably unrelated but i insert it just in case. It is a shredder one and it was only 2 line. I was initially thinking i was not able to type but eventually the "continue" i typed appeared (but dit nothing). The KDL was unresponsive like when webpositive is stuck in a script. My virtual memory was still disabled at that time (not sure if it is releated, i have 8G of memory). rebooted, enables VM again and rebooted so that it take effect. From that point, not crash at all.

by AlienSoldier, 4 weeks ago

Attachment: DSC00287.JPG added

comment:4 by waddlesplash, 4 weeks ago

Milestone: UnscheduledR1/beta6
Resolution: fixed
Status: newclosed

This screenshot is an app_server or input_server crash, not a kernel crash. If it happens again, you can type "save-report" at the prompt to save a report to desktop that should be available on reboot.

So, it's a different issue indeed. Thanks for testing!

Note: See TracTickets for help on using tickets.