Comment 6 for bug 1757517
Revision history for this message
|
|
#6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Ping?
This hit us again today in a different context: Chrome uses 128K thread stacks, which is normally plenty.
But when instrumented for profiling, the counters reside in TLS, and consumed most of the 128K stack, resulting in a crash that was hard to diagnose.
We then had to change the source before instrumented Chrome could run.
It would be nice if glibc just did the right thing, getting rid of the crash and the need to modify sources.