Opened 17 years ago
Closed 17 years ago
#1122 closed bug (fixed)
Kernel idle thread mixup
| Reported by: | jonas.kirilla | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Servers/app_server | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | bonefish | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Somehow a userland thread has replaced or tainted(?) the kernel team's idle thread.
I suppose it's the app_server window thread for the Mail application. Mail is no longer running. I don't recall if it crashed or not. I don't think it did.
See screenshots.
Attachments (3)
Change History (7)
by , 17 years ago
| Attachment: | screen5.png added |
|---|
by , 17 years ago
| Attachment: | screen6.png added |
|---|
by , 17 years ago
| Attachment: | screen7.png added |
|---|
comment:1 by , 17 years ago
| Cc: | added |
|---|
comment:2 by , 17 years ago
Forgot to add: The first thing the ServerWindow constructor does is invoking SetTitle() (which definitely happens before Run()), so it's actually pretty likely that a random thread is renamed.
comment:3 by , 17 years ago
| Component: | System/Kernel → Servers/app_server |
|---|
comment:4 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
According to your "top", the thread ID is 1, so it probably has only been renamed. Given the name, I tend to blame the app server. My best guess would be that ServerWindow::SetTitle() has been invoked before MessageLooper::Run(). Since MessageLooper::fThread is not initialized in the constructor, it might have any value (even 1) in that case.