java中线程是在堆，还是在栈上实现？

2005-11-21 10:10:00 732 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›

Delphi XE开发Linux应用（一） Delphi是我常用的开发工具，使用C语言开发Linux应用当然高效，但是对于数据库的操作等方面还是不方便，开发的速度和功能和Delphi比起来还是相差甚远。因此我选择使用Delphi XE进行Linuxde开发，Delphi xe开发Linux以下应用非常方便当然也可以使用Linux下的容器技术进行管理。WebBroker。阅读详情

判断线程运行在堆，还是在栈上的依据是什么？

...全文

Firemonkey使用iOS的第三方静态库（Link Binary With Libraries）最近需要从内存流中直接播放音频，想到了使用第三方音频播放库bass。在windows上可以很方便的使用相应动态库（具体参考万一的博客），但在iOS上却没有相应的使用介绍，准确的说是没有用于Firemonkey上的示例。在它官方论坛找到一个用于OSX的Demo，通过分析和测试，研究出了Firemonkey在iOS开发上使用第三方静态库的流程和方法。下面以在Delphi XE10上使用bass的静态库... 阅读详情

enator

Java 51,407 成员 86,130 内容

+ 关注 + 加入社区

切换为时间正序

beihehuaiyu 2005-12-18

打赏
举报

《Thinking In Java》

Where storage lives
It’s useful to visualize some aspects of how things are laid out while the program is running—in particular how memory is arranged. There are six different places to store data: Feedback

Registers. This is the fastest storage because it exists in a place different from that of other storage: inside the processor. However, the number of registers is severely limited, so registers are allocated by the compiler according to its needs. You don’t have direct control, nor do you see any evidence in your programs that registers even exist. Feedback
The stack. This lives in the general random-access memory (RAM) area, but has direct support from the processor via its stack pointer. The stack pointer is moved down to create new memory and moved up to release that memory. This is an extremely fast and efficient way to allocate storage, second only to registers. The Java compiler must know, while it is creating the program, the exact size and lifetime of all the data that is stored on the stack, because it must generate the code to move the stack pointer up and down. This constraint places limits on the flexibility of your programs, so while some Java storage exists on the stack—in particular, object references—Java objects themselves are not placed on the stack. Feedback
The heap. This is a general-purpose pool of memory (also in the RAM area) where all Java objects live. The nice thing about the heap is that, unlike the stack, the compiler doesn’t need to know how much storage it needs to allocate from the heap or how long that storage must stay on the heap. Thus, there’s a great deal of flexibility in using storage on the heap. Whenever you need to create an object, you simply write the code to create it by using new, and the storage is allocated on the heap when that code is executed. Of course there’s a price you pay for this flexibility. It takes more time to allocate heap storage than it does to allocate stack storage (if you even could create objects on the stack in Java, as you can in C++). Feedback
Static storage. “Static” is used here in the sense of “in a fixed location” (although it’s also in RAM). Static storage contains data that is available for the entire time a program is running. You can use the static keyword to specify that a particular element of an object is static, but Java objects themselves are never placed in static storage. Feedback
Constant storage. Constant values are often placed directly in the program code, which is safe since they can never change. Sometimes constants are cordoned off by themselves so that they can be optionally placed in read-only memory (ROM), in embedded systems. Feedback
Non-RAM storage. If data lives completely outside a program, it can exist while the program is not running, outside the control of the program. The two primary examples of this are streamed objects, in which objects are turned into streams of bytes, generally to be sent to another machine, and persistent objects, in which the objects are placed on disk so they will hold their state even when the program is terminated. The trick with these types of storage is turning the objects into something that can exist on the other medium, and yet can be resurrected into a regular RAM-based object when necessary. Java provides support for lightweight persistence, and future versions of Java might provide more complete solutions for persistence. Feedback

kongfh 2005-12-16

打赏
举报

java中基本类型在栈中分配，而对象的内存都是分配在堆中，其引用存储在栈中。

mfyl 2005-12-12

打赏
举报

mark

kof11321 2005-11-29

打赏
举报

每一个java线程都拥有自己的内存栈，用来存放局部变量和返回值，所有的线程共享一个内存堆(heap)

nbshiny 2005-11-29

打赏
举报

怎么判断是建立在堆上或者是在栈上，请问什么东西是利用了栈，谢谢？

lesstif 2005-11-22

打赏
举报

use setDeamon(true) to make it on stack, otherwise, it is a heap implementation

nighthawk 2005-11-22

打赏
举报

heap

ahFaye 2005-11-22

打赏
举报

如果在栈上那先进栈的线程不是一定要后出栈
显然不行

speedd55503 2005-11-21

打赏
举报

本人认为如果是用“new”出来的就应该在堆上

gemouzhi 2005-11-21

打赏
举报

线程当然是堆，这还用问吗？

java中线程是在堆，还是在栈上实现？

相关推荐